Skip to content

Conversation

@maropu
Copy link
Member

@maropu maropu commented May 22, 2020

What changes were proposed in this pull request?

This PR intends to add trivial tests to check #27024 has already been fixed in the master.

Closes #27024

Why are the changes needed?

For test coverage.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Added tests.

@maropu
Copy link
Member Author

maropu commented May 22, 2020

@cloud-fan @gengliangwang I've checked the proposal in #27024 again and I think it's been already fixed in the master. So, we could close SPARK-29854 now. Just in case, I opened this PR to add trivial tests to check that. But, closing this PR looks okay if not needed. Could you check this?


setupTestData()

test("lpad/rpad should throw an exception for invalid length input if the ANSI mode enabled") {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @maropu .
Can we add these new test coverage into string-functions.sql instead of SQLQuerySuite?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For ansi, you can create a new string-functions.sql under ansi directory.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM. Thank you, @maropu and @HyukjinKwon .

@SparkQA
Copy link

SparkQA commented May 22, 2020

Test build #122953 has finished for PR 28604 at commit 4615923.

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

@SparkQA
Copy link

SparkQA commented May 22, 2020

Test build #122960 has finished for PR 28604 at commit fae1cf4.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented May 22, 2020

Test build #122965 has finished for PR 28604 at commit ea9a527.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@cloud-fan
Copy link
Contributor

retest this please

@SparkQA
Copy link

SparkQA commented May 22, 2020

Test build #122978 has finished for PR 28604 at commit ea9a527.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@HyukjinKwon
Copy link
Member

retest this please

@SparkQA
Copy link

SparkQA commented May 22, 2020

Test build #123000 has finished for PR 28604 at commit ea9a527.

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

@maropu maropu closed this in 7ca73f0 May 22, 2020
maropu added a commit that referenced this pull request May 22, 2020
…tion for invalid length input

### What changes were proposed in this pull request?

This PR intends to add trivial tests to check #27024 has already been fixed in the master.

Closes #27024

### Why are the changes needed?

For test coverage.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Added tests.

Closes #28604 from maropu/SPARK-29854.

Authored-by: Takeshi Yamamuro <[email protected]>
Signed-off-by: Takeshi Yamamuro <[email protected]>
(cherry picked from commit 7ca73f0)
Signed-off-by: Takeshi Yamamuro <[email protected]>
@maropu
Copy link
Member Author

maropu commented May 22, 2020

Thanks, all! Merged to master/3.0.

@dongjoon-hyun
Copy link
Member

Hi, @maropu .
This seems to break branch-3.0. Could you make a follow-up with the regenerated output?

@dongjoon-hyun
Copy link
Member

Since it's trivial, I regenerated it and made a hotfix followup commit to recover branch-3.0 Jenkins jobs.

@maropu
Copy link
Member Author

maropu commented May 23, 2020

Ah, sorry for that... Thanks for the update, anyway.

@dongjoon-hyun
Copy link
Member

No problem~, @maropu .

@maropu
Copy link
Member Author

maropu commented May 23, 2020

I should be more careful when merging PRs into branch-3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants