-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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
[SPARK-32836][SS][TESTS] Fix DataStreamReaderWriterSuite to check writer options correctly #29701
Conversation
…ter options correctly
.format("org.apache.spark.sql.streaming.test") | ||
.option("opt1", "1") | ||
.options(Map("opt2" -> "2")) |
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.
Previously, the test case used the same options here and line 162~163. This hides this test coverage bug.
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.
good catch!
cc @cloud-fan and @HeartSaVioR |
Thank you, @cloud-fan ! |
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.
LGTM assuming tests will pass.
Thank you, @HeartSaVioR . |
Thank you, @viirya . Merged to master/3.0/2.4. |
…ter options correctly ### What changes were proposed in this pull request? This PR aims to fix the test coverage at `DataStreamReaderWriterSuite`. ### Why are the changes needed? Currently, the test case checks `DataStreamReader` options instead of `DataStreamWriter` options. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the revised test case. Closes #29701 from dongjoon-hyun/SPARK-32836. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 06a9945) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
…ter options correctly ### What changes were proposed in this pull request? This PR aims to fix the test coverage at `DataStreamReaderWriterSuite`. ### Why are the changes needed? Currently, the test case checks `DataStreamReader` options instead of `DataStreamWriter` options. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the revised test case. Closes #29701 from dongjoon-hyun/SPARK-32836. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 06a9945) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
Test build #128473 has finished for PR 29701 at commit
|
@dongjoon-hyun The test seems not passed? |
Ur, let me check again. I checked in IntelliJ and run |
BTW, |
I verified again locally. It works. Given the error message from Jenkins, the map seems to be overwritten to the read options back again by the streaming query. If not, it should fail before reaching
To sum up, this looks like a long-standing flakiness between |
Ok, I think it is fine as GitHub Actions passed. |
Ya. It looks okay for now.
|
…ter options correctly ### What changes were proposed in this pull request? This PR aims to fix the test coverage at `DataStreamReaderWriterSuite`. ### Why are the changes needed? Currently, the test case checks `DataStreamReader` options instead of `DataStreamWriter` options. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the revised test case. Closes apache#29701 from dongjoon-hyun/SPARK-32836. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 06a9945) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
What changes were proposed in this pull request?
This PR aims to fix the test coverage at
DataStreamReaderWriterSuite
.Why are the changes needed?
Currently, the test case checks
DataStreamReader
options instead ofDataStreamWriter
options.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the revised test case.