Skip to content

[SPARK-33067][SQL][TESTS][FOLLOWUP] Check error messages in JDBCTableCatalogSuite #29957

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

Closed

Conversation

MaxGekk
Copy link
Member

@MaxGekk MaxGekk commented Oct 6, 2020

What changes were proposed in this pull request?

Get error message from the expected exception, and check that they are reasonable.

Why are the changes needed?

To improve tests by expecting particular error messages.

Does this PR introduce any user-facing change?

No

How was this patch tested?

By running JDBCTableCatalogSuite.

@MaxGekk
Copy link
Member Author

MaxGekk commented Oct 6, 2020

@HyukjinKwon Please, take a look at this follow up PR. I addressed @cloud-fan 's comments from #29912 (comment)

@SparkQA
Copy link

SparkQA commented Oct 6, 2020

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34063/

@SparkQA
Copy link

SparkQA commented Oct 6, 2020

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/34063/

@SparkQA
Copy link

SparkQA commented Oct 6, 2020

Test build #129456 has finished for PR 29957 at commit 3db9812.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@HyukjinKwon
Copy link
Member

Merged to master.

@MaxGekk MaxGekk deleted the jdbcv2-negative-tests-followup branch December 11, 2020 20:28
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

Successfully merging this pull request may close these issues.

3 participants