You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Craig McIntosh (JIRA)" <ji...@apache.org> on 2016/05/16 18:19:13 UTC

[jira] [Commented] (SAMZA-469) Support Scala 2.11

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

Craig McIntosh commented on SAMZA-469:
--------------------------------------

Has a decision to move away from Scala been made and is there a timeframe for the move?  If not a 2.11 or 2.12 version would be really helpful.

My concern is that with 2.12 coming up soon, other Scala libraries we use in our Samza jobs will stop cross compiling to 2.10 in the near future.   

> Support Scala 2.11
> ------------------
>
>                 Key: SAMZA-469
>                 URL: https://issues.apache.org/jira/browse/SAMZA-469
>             Project: Samza
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>            Assignee: Tim Harper
>              Labels: jdk7
>         Attachments: 0001-SAMZA-469-Support-Scala-2.11.patch, 0001-SAMZA-469-Support-Scala-2.11.patch
>
>
> SAMZA-430 updated Samza to remove legacy Scala 2.9.2 code. We should upgrade Samza to build and default to Scala 2.11. This will require us waiting for Kafka 0.8.2 to be released, as it appears to be the [first version to support Scala 2.11|http://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11] (KAFKA-1419).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)