Bug #71613 Backwards compatibility not being supported causing customer upgrade issues

• Submitted: 6 Feb 2014 21:16
• Modified: 7 Feb 2014 6:27
• Reporter: Indira Iyer
• Status: Duplicate
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.6.14
• OS: Windows
• CPU Architecture: Any

[6 Feb 2014 21:16] Indira Iyer

Description:
Bug # 68453: InnoDB indexes no longer silently truncated to 767 bytes, produce error instead, http://bugs.mysql.com/bug.php?id=68453, has been closed as not a bug. 

Despite the fact that the resolution to the bug suggests various workarounds, we consider this to be a bug, since it breaks backwards compatibility and forces products that relied on the previous behavior to have to make significant upgrade related changes when upgrading our product's DB version to 5.6.14 from an older version, 5.5.27. We have to not only massage the schema but also massage the data that was existing in the previous version of the database. Continued support of the previous behavior is desired, with configuration flags if necessary.

How to repeat:
Same as described in http://bugs.mysql.com/bug.php?id=68453 

Suggested fix:
Continued support of the previous behavior is desired, with configuration flags if necessary. i.e. based on configuration settings, do not throw errors if index size exceeds limits, instead truncate the index to the max allowed size.

[7 Feb 2014 6:28] MySQL Verification Team

Thank you for the bug report.
Reopened Bug #71613.
Marking this bug as duplicate of Bug #68453

[26 Aug 2014 0:13] Joe Mihalich

Hi,

   Is there a timeline of when this will be fixed?

Thanks,
Joe