You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@predictionio.apache.org by "Pat Ferrel (JIRA)" <ji...@apache.org> on 2016/08/30 18:12:20 UTC

[jira] [Comment Edited] (PIO-30) Cross build for different versions of scala and spark

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

Pat Ferrel edited comment on PIO-30 at 8/30/16 6:11 PM:
--------------------------------------------------------

Fine with me if we can do with cross-build but it's not just different libraries it will be different PIO code. There will need to be 2 binaries, and 2 sets of PIO source.

This is for Elasticsearch 2.x which is not even source compatible with 1.x. 


was (Author: pferrel):
Fine with me if we can do with cross-build but it's not just different libraries it will be different PIO code. There will need to be 2 binaries, and 2 sets of PIO source.

> 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
>
> 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.4#6332)