-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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-3982] [Streaming] [PySpark] Python API: receiverStream() #2833
Conversation
QA tests have started for PR 2833 at commit
|
QA tests have finished for PR 2833 at commit
|
Test FAILed. |
QA tests have started for PR 2833 at commit
|
QA tests have started for PR 2833 at commit
|
QA tests have finished for PR 2833 at commit
|
Test PASSed. |
Tests timed out for PR 2833 at commit |
QA tests have started for PR 2833 at commit
|
QA tests have finished for PR 2833 at commit
|
Just wondering when this pull request will be accepted? |
Taking a detailed look right now. |
QA tests have started for PR 2833 at commit
|
Tests timed out for PR 2833 at commit |
Test FAILed. |
Test build #480 has started for PR 2833 at commit
|
Test build #480 has finished for PR 2833 at commit
|
@davies Let's focus on this after Kafka Python API gets in. Since doing this the right way (that is running the receiver in the executor) is complicated, lets do a design doc and discussion on this. In the meantime, I leave it up to you to decide whether you want to leave this PR open. |
@tdas I think we could leave this PR open as a proposed approach, discuss the pro/con in docs. |
Alright, then could you come write up a design doc, post it on the JIRA and then we can discuss on it? |
Conflicts: streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
Test build #24871 has started for PR 2833 at commit
|
Test build #24872 has started for PR 2833 at commit
|
Test build #24871 has finished for PR 2833 at commit
|
Test PASSed. |
Test build #24872 has finished for PR 2833 at commit
|
Test PASSed. |
@davies Since we are not working on this feature any more mind closing this PR? We can open it once when we decide to focus on it. |
This patch brings receiverStream() for Python API, it could be used to create an input stream with any arbitrary user implemented receiver.
The Python receiver depends on py4j, so can only be run in driver (locally).
cc @tdas