[MDEV-16851] On schema mismatch in IMPORT TABLESPACE, display ROW_FORMAT in clear text - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Fix Version/s: 10.1.35, 10.2.17, 10.3.9
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Labels:
- compat56

Description

Oracle addressed Bug #27542720 SCHEMA MISMATCH - TABLE FLAGS DON'T MATCH, BUT FLAGS ARE NUMBERS in a peculiar way: replacing exact diagnostic output with less exact one.

Yes, hexadecimal flags may be user-friendly, but they may be crucial in diagnosing an issue. Adding more information (such as this) would be better:

ERROR HY000: Schema mismatch (Table flags don't match, server table has 0x23 and the meta-data file has 0x29; .cfg file uses ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8)

Attachments

Issue Links

blocks

MDEV-16850 Merge new release of InnoDB 5.7.23 to 10.2

Closed

relates to

MDEV-15049 Importing InnoDB table from 10.1 to 10.2 causes Schema mismatch (Expected FSP_SPACE_FLAGS=0x21, .ibd file contains 0x0

Closed

MDEV-20930 Document that SHOW CREATE TABLE on InnoDB tables only shows ROW_FORMAT when explicitly set

Closed

MDEV-20974 Don't require .cfg files to import InnoDB tablespaces

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2018-07-30 10:04

Updated:: 2019-11-04 21:16

Resolved:: 2018-07-30 11:13

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.