diff options
| author | Prashant Sharma <prashsh1@in.ibm.com> | 2016-06-13 11:13:09 -0700 |
|---|---|---|
| committer | Shixiong Zhu <shixiong@databricks.com> | 2016-06-13 11:13:09 -0700 |
| commit | 4134653e53adde72f53c61929473dcacae9be8b6 (patch) | |
| tree | 995c57ad0cc343fdcd759000cab4a6a51fb6834c /repl/scala-2.10 | |
| parent | 938434dc78f35f77cdebd15dcce8d5e7871b396b (diff) | |
| download | spark-4134653e53adde72f53c61929473dcacae9be8b6.tar.gz spark-4134653e53adde72f53c61929473dcacae9be8b6.tar.bz2 spark-4134653e53adde72f53c61929473dcacae9be8b6.zip | |
[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", "javap", "power", "type", "kind". As they are useful and fully functional and part of scala/scala project, I see no harm in having them either.
Verbatim paste form JIRA 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.
## How was this patch tested?
Existing tests and manual, by trying out all of the above commands.
P.S. Symantics of reset are to be discussed in a separate issue.
Author: Prashant Sharma <prashsh1@in.ibm.com>
Closes #13437 from ScrapCodes/SPARK-15697/repl-unblock-commands.
Diffstat (limited to 'repl/scala-2.10')
0 files changed, 0 insertions, 0 deletions