cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From koushik-das <>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-9340: General DB Optimization
Date Wed, 04 May 2016 05:54:04 GMT
Github user koushik-das commented on the pull request:
    I am getting this error during deploy DB "Specified key was too long; max key length is
767 bytes". I have provided another inline comment in the code which is failing. Mysql version
is 5.6.12.
    ========> Processing upgrade:
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    	at java.lang.reflect.Method.invoke(
    	at org.codehaus.mojo.exec.ExecJavaMojo$
    Caused by: Unable to upgrade the database
    	... 6 more
    Caused by: Unable to execute upgrade
script: /Users/koushik/code/cloudstack-apache/cloudstack/developer/target/db/db/schema-481to490.sql
    	... 8 more
    Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was
too long; max key length is 767 bytes
    	... 9 more
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 40.361 s
    [INFO] Finished at: 2016-05-04T11:07:42+05:30
    [INFO] Final Memory: 70M/263M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema)
on project cloud-developer: An exception occured while executing the Java class. null: InvocationTargetException:
Unable to upgrade the database: Unable to execute upgrade script: /Users/koushik/code/cloudstack-apache/cloudstack/developer/target/db/db/schema-481to490.sql:
Specified key was too long; max key length is 767 bytes -> [Help 1]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] For more information about the errors and possible solutions, please read the
following articles:
    [ERROR] [Help 1]

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message