Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14340
@rxin,
Production streaming jobs can be written in Python and me and my company
are example.
I wrote a little bit more in Jira. I think it's better place for discussion.
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/14340
Thanks a lot @rxin for your comments, let me close it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14340
So I would like to -1 this patch. I think it's been a mistake to support
dstream in Python -- yes it satisfies a checkbox and Spark could claim there's
support for streaming in Python. However, the
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/14340
@jerryshao agreed that this is probably as good as possible for the Python
api and the limitations make sense
Generally LGTM, the only remaining comments I had were minor wording things.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62877/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62877 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62877/consoleFull)**
for PR 14340 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62877 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62877/consoleFull)**
for PR 14340 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62871/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62871 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62871/consoleFull)**
for PR 14340 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62871 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62871/consoleFull)**
for PR 14340 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/14340
Thanks a lot @koeninger for your review, I think it is not so flexible for
Python API to achieve same functionalities as Java/Scala APIs, especially for
things like extended class like
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62870/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62870 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62870/consoleFull)**
for PR 14340 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62870 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62870/consoleFull)**
for PR 14340 at commit
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/14340
In terms of feature parity, are we OK with telling python users they are
out of luck if they need something not covered by Assign / Subscribe /
SubscribePattern? For scala / java users they can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62822/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62822 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62822/consoleFull)**
for PR 14340 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62822 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62822/consoleFull)**
for PR 14340 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62807 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62807/consoleFull)**
for PR 14340 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62807/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62807 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62807/consoleFull)**
for PR 14340 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/14340
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62795 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62795/consoleFull)**
for PR 14340 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62795/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62795 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62795/consoleFull)**
for PR 14340 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14340
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62784/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62784 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62784/consoleFull)**
for PR 14340 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14340
**[Test build #62784 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62784/consoleFull)**
for PR 14340 at commit
35 matches
Mail list logo
