8000 About MySQL SQL Limitations Warning · keycloak keycloak · Discussion #20460 · GitHub
[go: up one dir, main page]

Skip to content
{"@context":"https://schema.org","@type":"QAPage","mainEntity":{"@type":"Question","name":"About MySQL SQL Limitations Warning","text":"\u003cp dir=\"auto\"\u003eHello,\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThese warnings repeat 4 times in the keycloak log. It causes more than 5 minutes delay until keycloak reachable.\u003c/p\u003e\n\u003cdiv class=\"highlight highlight-source-shell notranslate position-relative overflow-auto\" dir=\"auto\" data-snippet-clipboard-copy-content=\"2023-05-19 14:28:25,288 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: node_240035, Site name: null\n2023-05-19 14:28:25,986 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, modifyDataType will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use \u0026lt;sql\u0026gt; or \u0026lt;modifySql\u0026gt; to re-specify all configuration if this is the case\n2023-05-19 14:28:25,986 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use \u0026lt;sql\u0026gt; or \u0026lt;modifySql\u0026gt; to re-specify all configuration if this is the case\n2023-05-19 14:28:26,433 INFO [org.keycloak.quarkus.runtime.storage.legacy.liquibase.QuarkusJpaUpdaterProvider] (main) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml\n2023-05-19 14:28:26,895 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, modifyDataType will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use \u0026lt;sql\u0026gt; or \u0026lt;modifySql\u0026gt; to re-specify all configuration if this is the case\n2023-05-19 14:28:26,896 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use \u0026lt;sql\u0026gt; or \u0026lt;modifySql\u0026gt; to re-specify all configuration if this is the case\n2023-05-19 14:30:53,602 INFO [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener\n2023-05-19 14:30:53,614 INFO [org.keycloak.services] (main) KC-SERVICES0050: Initializing master realm\"\u003e\u003cpre class=\"notranslate\"\u003e2023-05-19 14:28:25,288 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: node_240035, Site name: null\n2023-05-19 14:28:25,986 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, modifyDataType will lose primary key/autoincrement/not null/comment settings explicitly redefined \u003cspan class=\"pl-k\"\u003ein\u003c/span\u003e the change. Use \u003cspan class=\"pl-k\"\u003e\u0026lt;\u003c/span\u003esql\u003cspan class=\"pl-k\"\u003e\u0026gt;\u003c/span\u003e or \u003cspan class=\"pl-k\"\u003e\u0026lt;\u003c/span\u003emodifySql\u003cspan class=\"pl-k\"\u003e\u0026gt;\u003c/span\u003e to re-specify all configuration \u003cspan class=\"pl-k\"\u003eif\u003c/span\u003e this is the \u003cspan class=\"pl-k\"\u003ecase\u003c/span\u003e\n2023-05-19 14:28:25,986 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined \u003cspan class=\"pl-k\"\u003ein\u003c/span\u003e the change. Use \u0026lt;sql\u0026gt; or \u0026lt;modifySql\u0026gt; to re-specify all configuration if this is the case\n2023-05-19 14:28:26,433 INFO [org.keycloak.quarkus.runtime.storage.legacy.liquibase.QuarkusJpaUpdaterProvider] (main) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml\n2023-05-19 14:28:26,895 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, modifyDataType will lose primary key/autoincrement/not null/comment settings explicitly redefined \u003cspan class=\"pl-k\"\u003ein\u003c/span\u003e the change. Use \u003cspan class=\"pl-k\"\u003e\u0026lt;\u003c/span\u003esql\u003cspan class=\"pl-k\"\u003e\u0026gt;\u003c/span\u003e or \u003cspan class=\"pl-k\"\u003e\u0026lt;\u003c/span\u003emodifySql\u003cspan class=\"pl-k\"\u003e\u0026gt;\u003c/span\u003e to re-specify all configuration \u003cspan class=\"pl-k\"\u003eif\u003c/span\u003e this is the \u003cspan class=\"pl-k\"\u003ecase\u003c/span\u003e\n2023-05-19 14:28:26,896 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined \u003cspan class=\"pl-k\"\u003ein\u003c/span\u003e the change. Use \u0026lt;sql\u0026gt; or \u0026lt;modifySql\u0026gt; to re-specify all configuration if this is the case\n2023-05-19 14:30:53,602 INFO [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener\n2023-05-19 14:30:53,614 INFO [org.keycloak.services] (main) KC-SERVICES0050: Initializing master realm\u003c/pre\u003e\u003c/div\u003e\n\u003cp dir=\"auto\"\u003eThe database already configured for keycloak database, db user and db password. They are running in k8s, and there is no resource limit to prevent any operation.\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eDo you have any suggestions to remove this warnings?\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThanks 😊\u003c/p\u003e","upvoteCount":2,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"\u003cp dir=\"auto\"\u003eWell done, \u003ca class=\"user-mention notranslate\" data-hovercard-type=\"user\" data-hovercard-url=\"/users/rection/hovercard\" data-octo-click=\"hovercard-link-click\" data-octo-dimensions=\"link_type:self\" href=\"https://github.com/rection\"\u003e@rection\u003c/a\u003e !\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThanks for clarifying the scenario in the new Issue's description.\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eI'm gonna take a look at it. Follow the comments there from now.\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThanks.\u003c/p\u003e","upvoteCount":0,"url":"https://github.com/keycloak/keycloak/discussions/20460#discussioncomment-6100478"}}}
Discussion options

You must be logged in to vote

Well done, @rection !

Thanks for clarifying the scenario in the new Issue's description.

I'm gonna take a look at it. Follow the comments there from now.

Thanks.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@bayars
Comment options

@andre-nascimento6791
Comment options

Answer selected by bayars
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
0