Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-09 Thread Trevor Grant
ivial. > > > > Sent from my Verizon Wireless 4G LTE smartphone > > > Original message > From: Pat Ferrel > Date: 07/07/2017 10:35 PM (GMT-08:00) > To: dev@mahout.apache.org > Cc: Holden Karau , u...@mahout.apache.org, > Dmitriy Lyubimov , Andrew

RE: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-08 Thread Andrew Palumbo
...@mahout.apache.org, Dmitriy Lyubimov , Andrew Palumbo Subject: Re: [DISCUSS] Naming convention for multiple spark/scala combos IIRC these all fit sbt’s conventons? On Jul 7, 2017, at 2:05 PM, Trevor Grant wrote: So to tie all of this together- org.apache.mahout:mahout-spark_2.10:0.13.1_spark_1_6

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Pat Ferrel
k the _spark1 / _spark2 is probably the right way (or > _spark_1 / _spark_2 is fine too). > > > On Fri, Jul 7, 2017 at 11:43 AM, Trevor Grant > wrote: > >> >> -- Forwarded message -- >> From: Andrew Palumbo >> Date: Fri, Jul 7, 2017 at 12:28 PM >> Subj

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Andrew Musselman
martphone > > > > > > Original message > > From: Holden Karau > > Date: 07/07/2017 1:24 PM (GMT-08:00) > > To: dev@mahout.apache.org > > Cc: Trevor Grant > > Subject: Re: [DISCUSS] Naming convention for multiple spark/scala combos > &g

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Holden Karau
/ _spark_2 is fine too). > > > On Fri, Jul 7, 2017 at 11:43 AM, Trevor Grant > wrote: > > > > > -- Forwarded message -- > > From: Andrew Palumbo > > Date: Fri, Jul 7, 2017 at 12:28 PM > > Subject: Re: [DISCUSS] Naming convention for multiple s

RE: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Andrew Palumbo
Welcome! Sent from my Verizon Wireless 4G LTE smartphone Original message From: Holden Karau Date: 07/07/2017 1:24 PM (GMT-08:00) To: dev@mahout.apache.org Cc: Trevor Grant Subject: Re: [DISCUSS] Naming convention for multiple spark/scala combos Trevor looped me in on

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Trevor Grant
17 at 11:43 AM, Trevor Grant > wrote: > >> >> -- Forwarded message -- >> From: Andrew Palumbo >> Date: Fri, Jul 7, 2017 at 12:28 PM >> Subject: Re: [DISCUSS] Naming convention for multiple spark/scala combos >> To: "dev@mahout.apache.org

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Holden Karau
s probably the right way (or _spark_1 / _spark_2 is fine too). On Fri, Jul 7, 2017 at 11:43 AM, Trevor Grant wrote: > > -- Forwarded message -- > From: Andrew Palumbo > Date: Fri, Jul 7, 2017 at 12:28 PM > Subject: Re: [DISCUSS] Naming convention for

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Andrew Palumbo
another option for artifact names (using jars for example here): mahout-spark-2.11_2.10-0.13.1.jar mahout-spark-2.11_2.11-0.13.1.jar mahout-math-scala-2.11_2.10-0.13.1.jar i.e. ---.jar not exactly pretty.. I somewhat prefer Trevor's idea of Dl4j convention. F

Re: [DISCUSS] Naming convention for multiple spark/scala combos

2017-07-07 Thread Dmitriy Lyubimov
it would seem 2nd option is preferable if doable. Any option that has most desirable combinations prebuilt, is preferable i guess. Spark itself also releases tons of hadoop profile binary variations. so i don't have to build one myself. On Fri, Jul 7, 2017 at 8:57 AM, Trevor Grant wrote: > Hey a