Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18395
I'll merge this and address Reynold's suggestions in a follow-up commit.
Merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18395
I plan to push this soon to unblock the next steps of the project. I'll
leave this open here a little bit in case anyone is still thinking about
commenting.
---
If your project is set up for it,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18395
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80222/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18395
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/18395
**[Test build #80222 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80222/testReport)**
for PR 18395 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18395
**[Test build #80222 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80222/testReport)**
for PR 18395 at commit
Github user jsoltren commented on the issue:
https://github.com/apache/spark/pull/18395
This looks fine to me. Though, I did have to ask Marcelo a number of
questions along the way to clarify what all was going on here. Maybe some of
the points I mention below should make their way
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18395
(Also, because this PR is not adding this package, just adding classes to
it, I'd rather do any package name change in a subsequent PR.)
---
If your project is set up for it, you can reply to this
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18395
@rxin
I wasn't planning on this being exposed at the moment; maybe in the future,
since this is sort of a "natural" extension point to allow different storage
backends for the UI / SHS.
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/18395
Is this going to be exposed?
Either way, we should find something like spark.util.kvstore package rather
than a top level package.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18395
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78479/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18395
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/18395
**[Test build #78479 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78479/testReport)**
for PR 18395 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18395
**[Test build #78479 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78479/testReport)**
for PR 18395 at commit
14 matches
Mail list logo
