Re: Removing Toree specific support for Python and R

2018-09-25 Thread Chip Senkbeil
They served as experiments in a time where the functionality may have been
useful, but that time has long since passed.

+1

On Tue, Sep 25, 2018, 9:19 PM Gino Bustelo  wrote:

> +1
>
> Spark’s support to share temp tables across sessions voids any need for
> this multi-Lang support.
>
> Gino B.
>
> > On Sep 25, 2018, at 2:20 PM, Corey Stubbs  wrote:
> >
> > +1
> >
> > On Tue, Sep 25, 2018, 13:10 Marius van Niekerk <
> marius.v.niek...@gmail.com>
> > wrote:
> >
> >> +1
> >>
> >> This would simplify usage, and remove a large class of python questions
> and
> >> confusion on our mailing list.  Several users assume that our R and
> Python
> >> featureset has parity with the primary kernels.
> >>
> >>> On Tue, 25 Sep 2018 at 12:46 kbat...@gmail.com 
> wrote:
> >>>
> >>> +1
> >>> The benefits that Luciano points out far outweigh the, probably
> >>> seldom-used, context sharing capabilities with limited features, IMHO.
> >>> This will eliminate an entire class of issues and questions while
> >> allowing
> >>> contributors to narrow their focus only on scala functionality and
> >>> improvements.
> >>>
>  On 2018/09/25 16:04:33, Luciano Resende  wrote:
>  Toree currently has some support for Python and R which are a thin
>  wrapper around what is provided in Spark. While this enables sharing
>  the Spark session and SQL Context between Scala and Python code, it
>  brings a huge gap on functionality when comparing with other Python
>  kernels like IPython and IRKernel. Adding to that, there is no
>  community member that is actively enhancing and contributing to these
>  two areas.
> 
>  Based on these, I would like to suggest the following to be done for
>  Toree 0.3.0 release timeframe:
>  - Remove Python and R support from Toree
>  - Document possible suggestions on Toree website (e.g. IPython,
>  IRKernel or others more active on their respective community)
> 
>  Some of the benefits:
>  - Avoid user confusion and frustration
>  - Improve kernel startup performance
>  - Cleaner code to maintain
> 
>  Please let me know your thoughts.
> 
>  [1]
> >>>
> >>
> https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb
> 
>  --
>  Luciano Resende
>  http://twitter.com/lresende1975
>  http://lresende.blogspot.com/
> 
> >>>
> >> --
> >> regards
> >> Marius van Niekerk
> >>
>


Re: Removing Toree specific support for Python and R

2018-09-25 Thread Gino Bustelo
+1

Spark’s support to share temp tables across sessions voids any need for this 
multi-Lang support. 

Gino B.

> On Sep 25, 2018, at 2:20 PM, Corey Stubbs  wrote:
> 
> +1
> 
> On Tue, Sep 25, 2018, 13:10 Marius van Niekerk 
> wrote:
> 
>> +1
>> 
>> This would simplify usage, and remove a large class of python questions and
>> confusion on our mailing list.  Several users assume that our R and Python
>> featureset has parity with the primary kernels.
>> 
>>> On Tue, 25 Sep 2018 at 12:46 kbat...@gmail.com  wrote:
>>> 
>>> +1
>>> The benefits that Luciano points out far outweigh the, probably
>>> seldom-used, context sharing capabilities with limited features, IMHO.
>>> This will eliminate an entire class of issues and questions while
>> allowing
>>> contributors to narrow their focus only on scala functionality and
>>> improvements.
>>> 
 On 2018/09/25 16:04:33, Luciano Resende  wrote:
 Toree currently has some support for Python and R which are a thin
 wrapper around what is provided in Spark. While this enables sharing
 the Spark session and SQL Context between Scala and Python code, it
 brings a huge gap on functionality when comparing with other Python
 kernels like IPython and IRKernel. Adding to that, there is no
 community member that is actively enhancing and contributing to these
 two areas.
 
 Based on these, I would like to suggest the following to be done for
 Toree 0.3.0 release timeframe:
 - Remove Python and R support from Toree
 - Document possible suggestions on Toree website (e.g. IPython,
 IRKernel or others more active on their respective community)
 
 Some of the benefits:
 - Avoid user confusion and frustration
 - Improve kernel startup performance
 - Cleaner code to maintain
 
 Please let me know your thoughts.
 
 [1]
>>> 
>> https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb
 
 --
 Luciano Resende
 http://twitter.com/lresende1975
 http://lresende.blogspot.com/
 
>>> 
>> --
>> regards
>> Marius van Niekerk
>> 


Re: Removing Toree specific support for Python and R

2018-09-25 Thread Corey Stubbs
+1

On Tue, Sep 25, 2018, 13:10 Marius van Niekerk 
wrote:

> +1
>
> This would simplify usage, and remove a large class of python questions and
> confusion on our mailing list.  Several users assume that our R and Python
> featureset has parity with the primary kernels.
>
> On Tue, 25 Sep 2018 at 12:46 kbat...@gmail.com  wrote:
>
> > +1
> > The benefits that Luciano points out far outweigh the, probably
> > seldom-used, context sharing capabilities with limited features, IMHO.
> > This will eliminate an entire class of issues and questions while
> allowing
> > contributors to narrow their focus only on scala functionality and
> > improvements.
> >
> > On 2018/09/25 16:04:33, Luciano Resende  wrote:
> > > Toree currently has some support for Python and R which are a thin
> > > wrapper around what is provided in Spark. While this enables sharing
> > > the Spark session and SQL Context between Scala and Python code, it
> > > brings a huge gap on functionality when comparing with other Python
> > > kernels like IPython and IRKernel. Adding to that, there is no
> > > community member that is actively enhancing and contributing to these
> > > two areas.
> > >
> > > Based on these, I would like to suggest the following to be done for
> > > Toree 0.3.0 release timeframe:
> > > - Remove Python and R support from Toree
> > > - Document possible suggestions on Toree website (e.g. IPython,
> > > IRKernel or others more active on their respective community)
> > >
> > > Some of the benefits:
> > > - Avoid user confusion and frustration
> > > - Improve kernel startup performance
> > > - Cleaner code to maintain
> > >
> > > Please let me know your thoughts.
> > >
> > > [1]
> >
> https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
> --
> regards
> Marius van Niekerk
>


[jira] [Resolved] (TOREE-474) support for custom resolvers (for %AddDeps)

2018-09-25 Thread Luciano Resende (JIRA)


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

Luciano Resende resolved TOREE-474.
---
   Resolution: Fixed
Fix Version/s: 0.3.0

> support for custom resolvers (for %AddDeps)
> ---
>
> Key: TOREE-474
> URL: https://issues.apache.org/jira/browse/TOREE-474
> Project: TOREE
>  Issue Type: Improvement
>  Components: Kernel
>Affects Versions: 0.2.0
>Reporter: Evgeniy Tokarev
>Assignee: Russell McEntyre
>Priority: Major
> Fix For: 0.3.0
>
>
> Jira has old issue like this https://issues.apache.org/jira/browse/TOREE-169 
> which was fixed at 0.1.0 but seems like 0.2.x doesn't as this functionality 
> anymore.
> Lot of libs using custom repositories like Bintray therefore seem like is a 
> big limitation of project 
> which doesn't allow to use custom repositories (Zeppelin and spark-notebooks 
> has that functionality) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (TOREE-474) support for custom resolvers (for %AddDeps)

2018-09-25 Thread Luciano Resende (JIRA)


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

Luciano Resende reassigned TOREE-474:
-

Assignee: Russell McEntyre

> support for custom resolvers (for %AddDeps)
> ---
>
> Key: TOREE-474
> URL: https://issues.apache.org/jira/browse/TOREE-474
> Project: TOREE
>  Issue Type: Improvement
>  Components: Kernel
>Affects Versions: 0.2.0
>Reporter: Evgeniy Tokarev
>Assignee: Russell McEntyre
>Priority: Major
> Fix For: 0.3.0
>
>
> Jira has old issue like this https://issues.apache.org/jira/browse/TOREE-169 
> which was fixed at 0.1.0 but seems like 0.2.x doesn't as this functionality 
> anymore.
> Lot of libs using custom repositories like Bintray therefore seem like is a 
> big limitation of project 
> which doesn't allow to use custom repositories (Zeppelin and spark-notebooks 
> has that functionality) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Removing Toree specific support for Python and R

2018-09-25 Thread kbates4
+1
The benefits that Luciano points out far outweigh the, probably seldom-used, 
context sharing capabilities with limited features, IMHO.  This will eliminate 
an entire class of issues and questions while allowing contributors to narrow 
their focus only on scala functionality and improvements.

On 2018/09/25 16:04:33, Luciano Resende  wrote: 
> Toree currently has some support for Python and R which are a thin
> wrapper around what is provided in Spark. While this enables sharing
> the Spark session and SQL Context between Scala and Python code, it
> brings a huge gap on functionality when comparing with other Python
> kernels like IPython and IRKernel. Adding to that, there is no
> community member that is actively enhancing and contributing to these
> two areas.
> 
> Based on these, I would like to suggest the following to be done for
> Toree 0.3.0 release timeframe:
> - Remove Python and R support from Toree
> - Document possible suggestions on Toree website (e.g. IPython,
> IRKernel or others more active on their respective community)
> 
> Some of the benefits:
> - Avoid user confusion and frustration
> - Improve kernel startup performance
> - Cleaner code to maintain
> 
> Please let me know your thoughts.
> 
> [1] 
> https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb
> 
> -- 
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
> 


[jira] [Commented] (TOREE-474) support for custom resolvers (for %AddDeps)

2018-09-25 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on TOREE-474:
--

Github user asfgit closed the pull request at:

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


> support for custom resolvers (for %AddDeps)
> ---
>
> Key: TOREE-474
> URL: https://issues.apache.org/jira/browse/TOREE-474
> Project: TOREE
>  Issue Type: Improvement
>  Components: Kernel
>Affects Versions: 0.2.0
>Reporter: Evgeniy Tokarev
>Priority: Major
>
> Jira has old issue like this https://issues.apache.org/jira/browse/TOREE-169 
> which was fixed at 0.1.0 but seems like 0.2.x doesn't as this functionality 
> anymore.
> Lot of libs using custom repositories like Bintray therefore seem like is a 
> big limitation of project 
> which doesn't allow to use custom repositories (Zeppelin and spark-notebooks 
> has that functionality) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Removing Toree specific support for Python and R

2018-09-25 Thread Ryan Blue
+1

After investigating the python support, we concluded that it's better to
use a normal ipython kernel. I think that the python Toree kernel would
take a lot of work to be on par with what already exists in Python.

On Tue, Sep 25, 2018 at 9:04 AM Luciano Resende 
wrote:

> Toree currently has some support for Python and R which are a thin
> wrapper around what is provided in Spark. While this enables sharing
> the Spark session and SQL Context between Scala and Python code, it
> brings a huge gap on functionality when comparing with other Python
> kernels like IPython and IRKernel. Adding to that, there is no
> community member that is actively enhancing and contributing to these
> two areas.
>
> Based on these, I would like to suggest the following to be done for
> Toree 0.3.0 release timeframe:
> - Remove Python and R support from Toree
> - Document possible suggestions on Toree website (e.g. IPython,
> IRKernel or others more active on their respective community)
>
> Some of the benefits:
> - Avoid user confusion and frustration
> - Improve kernel startup performance
> - Cleaner code to maintain
>
> Please let me know your thoughts.
>
> [1]
> https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>


-- 
Ryan Blue
Software Engineer
Netflix


Removing Toree specific support for Python and R

2018-09-25 Thread Luciano Resende
Toree currently has some support for Python and R which are a thin
wrapper around what is provided in Spark. While this enables sharing
the Spark session and SQL Context between Scala and Python code, it
brings a huge gap on functionality when comparing with other Python
kernels like IPython and IRKernel. Adding to that, there is no
community member that is actively enhancing and contributing to these
two areas.

Based on these, I would like to suggest the following to be done for
Toree 0.3.0 release timeframe:
- Remove Python and R support from Toree
- Document possible suggestions on Toree website (e.g. IPython,
IRKernel or others more active on their respective community)

Some of the benefits:
- Avoid user confusion and frustration
- Improve kernel startup performance
- Cleaner code to maintain

Please let me know your thoughts.

[1] 
https://github.com/apache/incubator-toree/blob/master/etc/examples/notebooks/sqlcontext_sharing.ipynb

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/