GitHub user ScrapCodes opened a pull request:

    https://github.com/apache/spark/pull/13661

    [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.
    
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ScrapCodes/spark repl-reset-command

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/13661.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #13661
    
----
commit 7f2e3b5ef6b0185591295ad24d08c7c86b6bd726
Author: Prashant Sharma <[email protected]>
Date:   2016-06-14T11:04:01Z

    [SPARK-15942][REPL] Unblock `:reset` command in REPL.

----


---
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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to