New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add version attribute in rule/schema/server.xml to help to identify config version #986
Labels
Milestone
Comments
sunsun314
added a commit
that referenced
this issue
Feb 19, 2019
yanhuqing666
added a commit
that referenced
this issue
Feb 19, 2019
#986 remove duplicate warning log
sunsun314
added a commit
that referenced
this issue
Feb 20, 2019
sunsun314
added a commit
that referenced
this issue
Feb 20, 2019
yanhuqing666
added a commit
that referenced
this issue
Feb 20, 2019
#986 add null check when try pull from zk
verified on dble version: 5.6.29-dble-9.9.9.9-e3b87339fe8b0d59538c27c01771ded840355091-20190220091638 |
sunsun314
added a commit
that referenced
this issue
Mar 7, 2019
sunsun314
added a commit
that referenced
this issue
Mar 7, 2019
yanhuqing666
pushed a commit
that referenced
this issue
Mar 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Well,when the dble-server be upgraded in some customer's environment ,there may be some errors occur because the config attribute has changed when the dble version changes. They may confused about what version the config file is and how to change to latest version config.
So we decide to add a version attribute in rule/schema/server.xml to help the user to identify the config version.DBLE would not stop user use outdated config ,only notify user with warning logs and dryrun results
The text was updated successfully, but these errors were encountered: