-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[SPARK-43031] [SS] [Connect] Enable unit test and doctest for streaming #40691
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
Changes from 1 commit
4d0fcdd
0ae7e33
b14fe81
17720b7
1e68a3c
dc05be8
c1674eb
23b9c93
60ddd01
e576821
26e2488
e25f7e6
aa1d4c2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -188,7 +188,8 @@ def awaitTermination(self, timeout: Optional[int] = None) -> Optional[bool]: | |
|
|
||
| Return whether the query has terminated or not within 5 seconds | ||
|
|
||
| >>> sq.awaitTermination(5) | ||
| TODO(SPARK-42960): remove the SKIP flag below | ||
| >>> sq.awaitTermination(5) # doctest: +SKIP | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why are these needed? This won't be tested in connect yet, right?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right.. This actually silents this line in the doctest for both connect and non-connect I believe (@HyukjinKwon please correct me if I'm wrong) , just some temporary pain we have to bear with as connect doesn't support this yet There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What is the pain? What fails if you remove this diff?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nothing fails but we skip some tests for also non-connect scenario There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Lets not skip any tests. Any skip should have a TODO comment.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sure! I've moved the TODO to the top of these methods to avoid them showing up in the PySpark doc
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we're absolutely sure that we will enable this back very soon, I am fine. As @rangadi said, I tried my best to avoid skipping the tests, but I did few times when I am about to enable it back very soon.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see. I think I'll just remove all of the SKIP flags and disable the doctest for now. Some of the functionalities might not be supported that soon I think. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Better solution is to comment out setting
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks! Done |
||
| False | ||
|
|
||
| >>> sq.stop() | ||
|
|
@@ -330,7 +331,9 @@ def stop(self) -> None: | |
| Stop streaming query | ||
|
|
||
| >>> sq.stop() | ||
| >>> sq.isActive | ||
|
|
||
| # TODO(SPARK-42940): remove the SKIP flag below | ||
| >>> sq.isActive # doctest: +SKIP | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this required? Why is it skipped?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Calling isActive after the query is stopped will throw error right now before the better session management is implemented There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is see, please add a TODO here with a brief comment. |
||
| False | ||
| """ | ||
| self._jsq.stop() | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
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.
Please ignore the change in this file. They are added and to be reviewed in #40689.