Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/13437
Does this also work for the 2.10 build?
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13437
No, that's too surprising. I'd expect all existing Spark state is
unchanged. If that's not possible I think we should leave it disabled.
---
If your project is set up for it, you can reply
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/13437
To reinitialize the SparkSession is pretty trivial, consequence would be on
`reset` all the executors will also be reset that is complete wipe of all the
data. I think that is expected
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13437
I think that if it returned the shell to its initial state with all objects
and config then `reset` works. I suppose it depends on how much work that is.
It doesn't seem worth much complexity
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/13437
About `reset` that holds true, but others were simply not functional in our
customized version of REPL. I will see if something can be done about reset
too.
Would you like the
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13437
What was the reasons each were disabled (if you know), and why are they OK
now?
For example, I know the reason we removed `reset` was because it removes
the `SparkContext` /
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13437
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59733/
Test
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13437
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13437
**[Test build #59733 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59733/consoleFull)**
for PR 13437 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13437
**[Test build #59733 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59733/consoleFull)**
for PR 13437 at commit
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/13437
[SPARK-15697] [REPL] Unblock some of the useful repl commands.
## What changes were proposed in this pull request?
Unblock some of the useful repl commands. like, "implicits",
11 matches
Mail list logo
