[ 
https://issues.apache.org/jira/browse/SPARK-15697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashant Sharma updated SPARK-15697:
------------------------------------
    Description: 
"implicits", "javap", "power", "type", "kind" commands in repl are blocked. 
However, they work fine in all cases I have tried. It is clear we don't support 
them as they are part of the scala/scala repl project. What is the harm in 
unblocking them, given they are useful ?
In previous versions of spark we disabled these commands because it was 
difficult to support them without customization and the associated maintenance. 
Since the code base of scala repl was actually ported and maintained under 
spark source. Now that is not the situation and one can benefit from these 
commands in Spark REPL as much as in scala repl.

Symantics of reset are to be discussed in a separate issue.

  was:
"implicits", "javap", "power", "type", "kind" commands in repl are blocked. 
However, they work fine in most cases. It is clear we don't support them they 
are part of the scala repl. What is the harm in unblocking them, given they are 
useful ?

In previous versions of spark we disabled these commands because it was 
difficult to support them with out customization and the associated maintenance 
burden. 

Symantics of reset are to be discussed in a separate issue.


> [SPARK REPL] unblock some of the useful repl commands.
> ------------------------------------------------------
>
>                 Key: SPARK-15697
>                 URL: https://issues.apache.org/jira/browse/SPARK-15697
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Shell
>    Affects Versions: 1.6.1
>            Reporter: Prashant Sharma
>            Priority: Trivial
>
> "implicits", "javap", "power", "type", "kind" commands in repl are blocked. 
> However, they work fine in all cases I have tried. It is clear we don't 
> support them as they are part of the scala/scala repl project. What is the 
> harm in unblocking them, given they are useful ?
> In previous versions of spark we disabled these commands because it was 
> difficult to support them without customization and the associated 
> maintenance. Since the code base of scala repl was actually ported and 
> maintained under spark source. Now that is not the situation and one can 
> benefit from these commands in Spark REPL as much as in scala repl.
> Symantics of reset are to be discussed in a separate issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to