Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user jose-torres commented on the issue:
https://github.com/apache/spark/pull/20752
There've been no comments on the doc. Should we move forward with this PR?
---
-
To unsubscribe, e-mail:
Github user jose-torres commented on the issue:
https://github.com/apache/spark/pull/20752
Doc sent to the dev list:
https://docs.google.com/document/d/1PJYfb68s2AG7joRWbhrgpEWhrsPqbhyRwUVl9V1wPOE
---
-
To
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88019/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88019 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88019/testReport)**
for PR 20752 at commit
Github user jose-torres commented on the issue:
https://github.com/apache/spark/pull/20752
Sounds fair to me. I'll continue iterating on the read side, and send out a
design proposal for the write side incorporating this discussion in the next
few days.
---
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/20752
> Right now, we're still at the point where we aren't quite sure what a
streaming API needs to look like. We're starting from basically ground zero;
the V1 streaming API just throws a DataFrame at
Github user jose-torres commented on the issue:
https://github.com/apache/spark/pull/20752
I agree that we should put a design for the streaming side on the dev list,
and I intend to do so. The streaming interfaces will remain evolving until a
design discussion about them has
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/20752
Thanks for the clear summary, @cloud-fan. I think we want to make it easy
to support batch, and then easy to reuse those internals to support streaming
by adding new mix-in interfaces. Streaming is
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/20752
I'm not very familiar with the streaming side, but here is my 2 cents: I
agree with @rdblue that it's unnecessary to introduce the epoch id to data
sources that don't care about streaming.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88019/testReport)**
for PR 20752 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88015/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Merged build finished. Test FAILed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88015 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88015/testReport)**
for PR 20752 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88015 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88015/testReport)**
for PR 20752 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Merged build finished. Test FAILed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88014 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88014/testReport)**
for PR 20752 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88014/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88014 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88014/testReport)**
for PR 20752 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88013 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88013/testReport)**
for PR 20752 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88013/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Merged build finished. Test FAILed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/20752
**[Test build #88013 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/88013/testReport)**
for PR 20752 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20752
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
25 matches
Mail list logo
