[ 
https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932273#comment-15932273
 ] 

ASF GitHub Bot commented on PIO-30:
-----------------------------------

Github user shimamoto commented on the issue:

    https://github.com/apache/incubator-predictionio/pull/364
  
    @dszeto I understand your situation.
    This PR is put EoM (Ease of Maintenance) before flexible because this leads 
to Easy of Extension in future. But as you say that the most important thing is 
flexible right now, this PR probably won't be able to achieve that goal. I 
think I will close this.
    
    The goal of us is that users can use the standard sets without building by 
themselves (i.e. without run `make-distribution.sh`), which is preferable that 
the latest. Otherwise users need to build, and this was going to be the next 
step. But I think that's a very hard thing to do right now.
    
    Please continue your good work.


> Cross build for different versions of scala and spark
> -----------------------------------------------------
>
>                 Key: PIO-30
>                 URL: https://issues.apache.org/jira/browse/PIO-30
>             Project: PredictionIO
>          Issue Type: Improvement
>            Reporter: Marcin ZiemiƄski
>            Assignee: Chan
>             Fix For: 0.11.0
>
>
> The present version of Scala is 2.10 and Spark is 1.4, which is quite old. 
> With Spark 2.0.0 come many performance improvements and features, that people 
> will definitely like to add to their templates. I am also aware that past 
> cannot be ignored and simply dumping 1.x might not be an option for other 
> users. 
> I propose setting up a crossbuild in sbt to build with scala 2.10 and Spark 
> 1.6 and a separate one for Scala 2.11 and Spark 2.0. Most of the files will 
> be consistent between versions including API. The problematic ones will be 
> divided between additional source directories: src/main/scala-2.10/ and 
> src/main/scala-2.11/. The dockerized tests should also take the two versions 
> into consideration



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

Reply via email to