Thanks a lot for point it out. I also found it in pom.xml.
A new ticket for reverting it has been submitted:
https://issues.apache.org/jira/browse/SPARK-4923
At first I assume that further development on it has been moved to
databricks cloud. But the JIRA ticket was already there in September. So
maybe demand on this API from the community is indeed low enough.
However, I would still suggest keeping it, even promoting it into a
Developer's API, this would encourage more projects to integrate in a
more flexible way, and save prototyping/QA cost by customizing fixtures
of REPL. People will still move to databricks cloud, which has far more
features than that. Many influential projects already depends on the
routinely published Scala-REPL (e.g. playFW), it would be strange for
Spark not doing the same.
What do you think?
Yours Peng
On 12/22/2014 04:57 PM, Sean Owen wrote:
Just closing the loop -- FWIW this was indeed on purpose --
https://issues.apache.org/jira/browse/SPARK-3452 . I take it that it's
not encouraged to depend on the REPL as a module.
On Sun, Dec 21, 2014 at 10:34 AM, Sean Owen <so...@cloudera.com> wrote:
I'm only speculating, but I wonder if it was on purpose? would people
ever build an app against the REPL?
On Sun, Dec 21, 2014 at 5:50 AM, Peng Cheng <pc...@uow.edu.au> wrote:
Everything else is there except spark-repl. Can someone check that out this
weekend?
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/spark-repl-1-2-0-was-not-uploaded-to-central-maven-repository-tp20799.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
For additional commands, e-mail: user-h...@spark.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
For additional commands, e-mail: user-h...@spark.apache.org
