-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-48172][SQL][FOLLOWUP] Fix escaping issues in JDBCDialects #46807
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
Conversation
|
@milastdbx Please take a look at this PR, problems were in #46588 as 3.4 and 3.5 are run with different JDK version. |
| connection.prepareStatement("INSERT INTO pattern_testing_table " | ||
| + "VALUES ('special_character_quote''_present')") | ||
| .executeUpdate() | ||
| connection.prepareStatement("INSERT INTO pattern_testing_table " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can these *not* values be collapsed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Collapsing them now would require changes in the ordering of results of tests in V2JDBCTest, as collapsing might reorder inputs, so maybe it is better to keep this change scoped to fixing the JDK problem for CI runs.
### What changes were proposed in this pull request? Removal of stripMargin from the code in `DockerJDBCIntegrationV2Suite`. ### Why are the changes needed? #46588 Given PR was merged to master/3.5/3.4. This PR broke daily jobs for `OracleIntegrationSuite`. Upon inspection, it was noted that 3.4 and 3.5 are run with JDK8 while master is run with JDK21 and stripMargin was behaving differently in those cases. Upon removing stripMargin and spliting `INSERT INTO` statements into multiple lines, all integration tests have passed. ### Does this PR introduce _any_ user-facing change? No, only loading of the test data was changed to follow language requirements. ### How was this patch tested? Existing suite was aborted in the job and now it is running. ### Was this patch authored or co-authored using generative AI tooling? No Closes #46806 Closes #46807 from mihailom-db/FixOracleMaster. Authored-by: Mihailo Milosevic <[email protected]> Signed-off-by: Kent Yao <[email protected]> (cherry picked from commit 4360ec7) Signed-off-by: Kent Yao <[email protected]>
### What changes were proposed in this pull request? Removal of stripMargin from the code in `DockerJDBCIntegrationV2Suite`. ### Why are the changes needed? #46588 Given PR was merged to master/3.5/3.4. This PR broke daily jobs for `OracleIntegrationSuite`. Upon inspection, it was noted that 3.4 and 3.5 are run with JDK8 while master is run with JDK21 and stripMargin was behaving differently in those cases. Upon removing stripMargin and spliting `INSERT INTO` statements into multiple lines, all integration tests have passed. ### Does this PR introduce _any_ user-facing change? No, only loading of the test data was changed to follow language requirements. ### How was this patch tested? Existing suite was aborted in the job and now it is running. ### Was this patch authored or co-authored using generative AI tooling? No Closes #46806 Closes #46807 from mihailom-db/FixOracleMaster. Authored-by: Mihailo Milosevic <[email protected]> Signed-off-by: Kent Yao <[email protected]> (cherry picked from commit 4360ec7) Signed-off-by: Kent Yao <[email protected]>
|
Merged to master/3.5/3.4. Thank you @mihailom-db |
What changes were proposed in this pull request?
Removal of stripMargin from the code in
DockerJDBCIntegrationV2Suite.Why are the changes needed?
#46588
Given PR was merged to master/3.5/3.4. This PR broke daily jobs for
OracleIntegrationSuite. Upon inspection, it was noted that 3.4 and 3.5 are run with JDK8 while master is run with JDK21 and stripMargin was behaving differently in those cases. Upon removing stripMargin and splitingINSERT INTOstatements into multiple lines, all integration tests have passed.Does this PR introduce any user-facing change?
No, only loading of the test data was changed to follow language requirements.
How was this patch tested?
Existing suite was aborted in the job and now it is running.
Was this patch authored or co-authored using generative AI tooling?
No
Closes #46806