Skip to content
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

inner DMP-6115 fixed: show which file cause error in dry-run. #2324

Closed
dcy10000 opened this issue Nov 25, 2020 · 0 comments
Closed

inner DMP-6115 fixed: show which file cause error in dry-run. #2324

dcy10000 opened this issue Nov 25, 2020 · 0 comments
Assignees
Milestone

Comments

@dcy10000
Copy link
Member

  • dble version:3.20.07.0
  • preconditions :
  1. an xml with wrong syntax.
  • configs:
    user.xml
    notice: the blacklist->name value is missing
<?xml version="1.0"?>
<!DOCTYPE dble:user SYSTEM "user.dtd">
<dble:user xmlns:dble="http://dble.cloud/" version="4.0">
    <managerUser name="root" password="******" ></managerUser>
    <shardingUser name="test2" schemas="testdb2" password="******" usingDecrypt="false"  readOnly="false" maxCon="800"></shardingUser>
    <blacklist name="">
        <property name="alterTableAllow">false</property>
    </blacklist>
</dble:user>

  • steps:
    step1. use the user config with the wrong syntax as listed above.
    step2. run dry-run command.

  • expect result:
    Show which config file cause the error.
    The response like this.
    [/user.xml] occurred parse errors, The detailed errors are as follows .org.xml.sax.SAXParseException; lineNumber: 13; columnNumber: 31; Attribute value "" of type NMTOKEN must be a name token.

  • real result:
    Doesn't know which config file causes the error.
    The reponse like this.
    org.xml.sax.SAXParseException; lineNumber: 13; columnNumber: 31; Attribute value "" of type NMTOKEN must be a name token.

@dcy10000 dcy10000 self-assigned this Nov 25, 2020
@yanhuqing666 yanhuqing666 added this to the 3.21.01.0 milestone Nov 26, 2020
@dcy10000 dcy10000 closed this as completed Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants