-
Bug
-
Resolution: Fixed
-
Medium
-
2.1.2
-
None
Stash 2.1.2 installation with MySQL is failing with this exception:
The schema could not be created. com.atlassian.stash.internal.migration.DefaultMigrationHelper.createSchema(DefaultMigrationHelper.java:117) com.atlassian.stash.internal.migration.AbstractMigrationMaintenanceTask.setup(AbstractMigrationMaintenanceTask.java:195) com.atlassian.stash.internal.maintenance.ActiveMaintenanceTaskContext.setup(ActiveMaintenanceTaskContext.java:166) ... Migration failed for change set liquibase/r1_3/m01.xml::STASHDEV-1023-10::bturner: Reason: liquibase.exception.DatabaseException: Error executing SQL CREATE INDEX `idx_sta_diff_comment_anchors` ON `stash`.`sta_diff_comment_anchor`(`to_hash`, `file_path`, `from_hash`): Specified key was too long; max key length is 767 bytes: Caused By: Error executing SQL CREATE INDEX `idx_sta_diff_comment_anchors` ON `stash`.`sta_diff_comment_anchor`(`to_hash`, `file_path`, `from_hash`): Specified key was too long; max key length is 767 bytes: Caused By: Specified key was too long; max key length is 767 bytes liquibase.changelog.ChangeSet.execute(ChangeSet.java:347) liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:27) liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) ... Error executing SQL CREATE INDEX `idx_sta_diff_comment_anchors` ON `stash`.`sta_diff_comment_anchor`(`to_hash`, `file_path`, `from_hash`): Specified key was too long; max key length is 767 bytes liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:62) liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:104) liquibase.database.AbstractDatabase.execute(AbstractDatabase.java:1091) ... Specified key was too long; max key length is 767 bytes sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
This has been reported on MySQL 5.6
This seems to have exceeded the Innodb limit of 767 bytes (40, 1024, 40) for (`to_hash`, `file_path`, `from_hash`).
- is related to
-
-
- Closed
-
[BSERV-3133] Stash 2.1.2 failing with MySQL 5.6 due to "specified key was too long" error
| Workflow | Original: Stash Workflow - Restricted [ 1444074 ] | New: JAC Bug Workflow v3 [ 3133983 ] |
| Workflow | Original: Stash Workflow [ 467004 ] | New: Stash Workflow - Restricted [ 1444074 ] |
The recently released MySQL 5.6.11 contains the fix for the query optimizer bug which prevented Stash from supporting 5.6.0 through 5.6.10. However, it introduces a new row ordering bug which affects, at a minimum, Stash's repository listings. As a result, Stash will not support 5.6.11 either.
| Fix Version/s | New: 2.2.0 [ 30796 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: To be reviewed [ 10026 ] | New: Closed [ 6 ] |
Stash 2.2 now explicitly handles MySQL 5.6. Note that it is still not supported, due to the optimizer bug. However, Stash 2.2 will now fail gracefully and with a sensible, clear error message when used with MySQL 5.6. Database migration and external database setup will both reject migrating to 5.6. For real MySQL 5.6 support, please watch STASH-3164
I have addressed all the schema-level issues, so the schema can now be created without issue. However, due to the aforementioned MySQL bug, I have also added code to the system which will explicitly prohibit using MySQL 5.6.0 through 5.6.10. It will block using those versions as migration or setup targets, and will also lock out the system if the connected MySQL instance is upgraded to one of them. The bug causes Stash's permission queries to return incorrect results, so it's pretty critical to the system that it be fixed.
| Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | New: Bryan Turner [ bturner ] |
The recently released MySQL 5.6.12 still contains the row ordering bug which affects 5.6.10 and 5.6.11. The MySQL team have confirmed this bug also affects all builds of the upcoming 5.7 as well. As a result, Stash will not support 5.6.12 either.