variable: Add innodb_default_row_format as noop

[morgo]

What problem does this PR solve?

Issue Number: fixes #23541

Problem Summary:

JIRA needs to be able to set innodb_default_row_format to function correctly. This adds it as a noop, which is safe to be able to do.

The innodb_file_format is also changed to be Barracuda, because Dynamic is only possible with Barracuda. Barracuda is also the default in MySQL 5.7, and file_formats become obsolete in MySQL 8.0.

What is changed and how it works?

What's Changed:

A noop sysvar was added: innodb_default_row_format.

Related changes

• None

Check List

Tests

• Integration test

Side effects

• Increased code complexity
• More "fake" metadata (although safe in this case)

Release note

• The system variable innodb_default_row_format was added for compatibility with Jira. Setting it has no effect.

[jackysp]

/lgtm

[morgo]

/run-check_dev_2

[djshow832]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• djshow832
• jackysp

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[zz-jason]

LGTM

[ti-chi-bot]

@zz-jason: Please use /LGTM instead of LGTM when you want to approve the pull request by comment.
If you use the GitHub review feature, please approve the PR directly, the comment will not take effect in the GitHub review feature.
If you have any qustions please refer to lgtm command help or lgtm plugin design.

If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 1.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[zz-jason]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: fb00bfc

[morgo]

/run-unit-test

[morgo]

/run-unit-test

[ti-chi-bot]

@morgo: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.