[SPARK-40811][SQL][TESTS] Use checkError() to intercept ParseException
#38267
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaxGekk
changed the title
checkError() to intercept ParseExceptioncheckError() to intercept ParseException
Member
Author
|
@panbingkun FYI |
Member
Author
|
@cloud-fan Could you approve this PR, please. |
cloud-fan
approved these changes
Oct 19, 2022
Member
Author
|
Merging to master. Thank you, @amaliujia and @cloud-fan for review. |
SandishKumarHN
pushed a commit
to SandishKumarHN/spark
that referenced
this pull request
Dec 12, 2022
…tion` ### What changes were proposed in this pull request? In the PR, I propose to port the following tests suites onto `checkError` to check valuable error parts instead of error messages: - JDBCWriteSuite - JDBCTableCatalogSuite - JdbcUtilsSuite - CreateTableAsSelectSuite - SparkScriptTransformationSuite - SQLViewSuite - InsertSuite ### Why are the changes needed? Migration on `checkError()` will make the tests independent from the text of error messages. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? By running the modified test suites: ``` $ build/sbt "test:testOnly *SQLViewSuite" $ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly org.apache.spark.sql.execution.datasources.v2.jdbc.JDBCTableCatalogSuite" $ build/sbt "test:testOnly *JdbcUtilsSuite" $ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *SparkScriptTransformationSuite" ``` Closes apache#38267 from MaxGekk/parseexception-checkError. Authored-by: Max Gekk <[email protected]> Signed-off-by: Max Gekk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
In the PR, I propose to port the following tests suites onto
checkErrorto check valuable error parts instead of error messages:Why are the changes needed?
Migration on
checkError()will make the tests independent from the text of error messages.Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the modified test suites: