Skip to content

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

Closed
MaxGekk wants to merge 1 commit into
apache:masterfrom
MaxGekk:jdbcv2-negative-tests-followup
Closed

MaxGekk wants to merge 1 commit into
apache:masterfrom
MaxGekk:jdbcv2-negative-tests-followup

Conversation

@MaxGekk

@MaxGekk MaxGekk commented Oct 6, 2020

Copy link
Copy Markdown
Member

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

MaxGekk commented Oct 6, 2020

Copy link
Copy Markdown
Member Author

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

@SparkQA

SparkQA commented Oct 6, 2020

Copy link
Copy Markdown

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

@SparkQA

SparkQA commented Oct 6, 2020

Copy link
Copy Markdown

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

@SparkQA

SparkQA commented Oct 6, 2020

Copy link
Copy Markdown

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
Copy Markdown
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