[jira] [Commented] (TOREE-375) Incorrect fully qualified name for spark context

2017-03-10 Thread Jakob Odersky (JIRA)

[ 
https://issues.apache.org/jira/browse/TOREE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905637#comment-15905637
 ] 

Jakob Odersky commented on TOREE-375:
-

Closing this as it is not related to Toree. I'll do some more investigation on 
the Spark and Scala shell sides.

> Incorrect fully qualified name for spark context
> 
>
> Key: TOREE-375
> URL: https://issues.apache.org/jira/browse/TOREE-375
> Project: TOREE
>  Issue Type: Bug
> Environment: Jupyter Notebook with Toree latest master 
> (1a9c11f5f1381c15b691a716acd0e1f0432a9a35) and Spark 2.0.2, Scala 2.11
>Reporter: Felix Schüler
>Priority: Critical
>
> When running below snippet in a cell I get a compile error for the MLContext 
> Constructor. Somehow the fully qualified name of the SparkContext gets messed 
> up. 
> The same does not happen when I start a Spark shell with the --jars command 
> and create the MLContext there.
> Snippet (the systemml jar is build with the latest master of SystemML):
> {code}
> %addjar 
> file:///home/felix/repos/incubator-systemml/target/systemml-0.13.0-incubating-SNAPSHOT.jar
>  -f
> import org.apache.sysml.api.mlcontext._
> import org.apache.sysml.api.mlcontext.ScriptFactory._
> val ml = new MLContext(sc)
> Starting download from 
> file:///home/felix/repos/incubator-systemml/target/systemml-0.13.0-incubating-SNAPSHOT.jar
> Finished download of systemml-0.13.0-incubating-SNAPSHOT.jar
> Name: Compile Error
> Message: :25: error: overloaded method constructor MLContext with 
> alternatives:
>   (x$1: 
> org.apache.spark.api.java.JavaSparkContext)org.apache.sysml.api.mlcontext.MLContext
>  
>   (x$1: 
> org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.SparkContext)org.apache.sysml.api.mlcontext.MLContext
>  cannot be applied to 
> (org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.SparkContext)
>val ml = new MLContext(sc)
> ^
> StackTrace: 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (TOREE-375) Incorrect fully qualified name for spark context

2017-03-10 Thread Jakob Odersky (JIRA)

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

Jakob Odersky closed TOREE-375.
---
Resolution: Done

> Incorrect fully qualified name for spark context
> 
>
> Key: TOREE-375
> URL: https://issues.apache.org/jira/browse/TOREE-375
> Project: TOREE
>  Issue Type: Bug
> Environment: Jupyter Notebook with Toree latest master 
> (1a9c11f5f1381c15b691a716acd0e1f0432a9a35) and Spark 2.0.2, Scala 2.11
>Reporter: Felix Schüler
>Priority: Critical
>
> When running below snippet in a cell I get a compile error for the MLContext 
> Constructor. Somehow the fully qualified name of the SparkContext gets messed 
> up. 
> The same does not happen when I start a Spark shell with the --jars command 
> and create the MLContext there.
> Snippet (the systemml jar is build with the latest master of SystemML):
> {code}
> %addjar 
> file:///home/felix/repos/incubator-systemml/target/systemml-0.13.0-incubating-SNAPSHOT.jar
>  -f
> import org.apache.sysml.api.mlcontext._
> import org.apache.sysml.api.mlcontext.ScriptFactory._
> val ml = new MLContext(sc)
> Starting download from 
> file:///home/felix/repos/incubator-systemml/target/systemml-0.13.0-incubating-SNAPSHOT.jar
> Finished download of systemml-0.13.0-incubating-SNAPSHOT.jar
> Name: Compile Error
> Message: :25: error: overloaded method constructor MLContext with 
> alternatives:
>   (x$1: 
> org.apache.spark.api.java.JavaSparkContext)org.apache.sysml.api.mlcontext.MLContext
>  
>   (x$1: 
> org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.SparkContext)org.apache.sysml.api.mlcontext.MLContext
>  cannot be applied to 
> (org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.org.apache.spark.SparkContext)
>val ml = new MLContext(sc)
> ^
> StackTrace: 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (TOREE-391) Messages to Jupyter kernel gateway are dropped in jeromq

2017-03-10 Thread Jim Rhyness (JIRA)

[ 
https://issues.apache.org/jira/browse/TOREE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904993#comment-15904993
 ] 

Jim Rhyness commented on TOREE-391:
---

https://github.com/apache/incubator-toree/pull/111

> Messages to Jupyter kernel gateway are dropped in jeromq
> 
>
> Key: TOREE-391
> URL: https://issues.apache.org/jira/browse/TOREE-391
> Project: TOREE
>  Issue Type: Bug
>Affects Versions: 0.1.0
> Environment: Linux ( RHEL 7.3 )
>Reporter: Jim Rhyness
>  Labels: newbie
>
> Kernel restart from Jupyter kernel gateway is failing with a timeout.  The 
> kernel is restarted, but kernel gateway times out waiting for a 
> kernel_info_reply message that it is
> expecting in response to kernel_info_request that it sends after initiating 
> the restart.
> The problem is reproducible most of the time with something like this:
> curl -v -X POST --data '{ "name":"apache_toree_scala" }'  
> http://127.0.0.1:/api/kernels
> curl -v -X POST --data '{}'  
> http://127.0.0.1:/api/kernels//restart
> From the IPython message protocol doc, this is the message format:
> [
>   b'u-u-i-d', # zmq identity(ies)
>   b'',   # delimiter
>   b'baddad42',# HMAC signature
>   b'{header}',# serialized header dict
>   b'{parent_header}', # serialized parent header dict
>   b'{metadata}',  # serialized metadata dict
>   b'{content},# serialized content dict
>   b'blob',# extra raw data buffer(s)
>   ...
> ]
> The first frame of the message contains zmq identities which, in some cases 
> in a Router-type socket, are generated by jeromq and then consist of five 
> bytes - 0 followed by a random int.
> In Toree, all frames are treated as Strings.  Conversion to UTF-8 corrupts 
> the zmq id, replacing non-UTF-8 characters by the replacement character 
> 0xEFBFBD.
> When the corrupted id is used in a message sent to the Router socket, the 
> peer to send the message to is not found and the message is dropped.
> This affects other messages as well, not just kernel_info_reply.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)