diff options
| author | Prashant Sharma <prashant@apache.org> | 2016-06-19 20:12:00 +0100 |
|---|---|---|
| committer | Sean Owen <sowen@cloudera.com> | 2016-06-19 20:12:00 +0100 |
| commit | 1b3a9b966a7813e2406dfb020e83605af22f9ef3 (patch) | |
| tree | f0f27fa3095a5cb3208f882ad141070fb80e3ae7 /docs/mllib-clustering.md | |
| parent | 001a58960311b07fe80e2f01e473f4987948d06e (diff) | |
| download | spark-1b3a9b966a7813e2406dfb020e83605af22f9ef3.tar.gz spark-1b3a9b966a7813e2406dfb020e83605af22f9ef3.tar.bz2 spark-1b3a9b966a7813e2406dfb020e83605af22f9ef3.zip | |
[SPARK-15942][REPL] Unblock `:reset` command in REPL.
## What changes were proposed in this pull
(Paste from JIRA issue.)
As a follow up for SPARK-15697, I have following semantics for `:reset` command.
On `:reset` we forget all that user has done but not the initialization of spark. To avoid confusion or make it more clear, we show the message `spark` and `sc` are not erased, infact they are in same state as they were left by previous operations done by the user.
While doing above, somewhere I felt that this is not usually what reset means. But an accidental shutdown of a cluster can be very costly, so may be in that sense this is less surprising and still useful.
## How was this patch tested?
Manually, by calling `:reset` command, by both altering the state of SparkContext and creating some local variables.
Author: Prashant Sharma <prashant@apache.org>
Author: Prashant Sharma <prashsh1@in.ibm.com>
Closes #13661 from ScrapCodes/repl-reset-command.
Diffstat (limited to 'docs/mllib-clustering.md')
0 files changed, 0 insertions, 0 deletions