You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Jongyoul Lee (JIRA)" <ji...@apache.org> on 2015/03/30 04:28:53 UTC
[jira] [Commented] (ZEPPELIN-9) Provide Spark profiles for older
1.2.x and 1.1.x versions
[ https://issues.apache.org/jira/browse/ZEPPELIN-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386105#comment-14386105 ]
Jongyoul Lee commented on ZEPPELIN-9:
-------------------------------------
[~rnowling] It's good suggestion but I don't know Zeppelin codes can be compatible for each version of Spark because Zeppelin becomes changed due to following the codes changed by Spark. [~moon] Do you think it's possible?
> Provide Spark profiles for older 1.2.x and 1.1.x versions
> ---------------------------------------------------------
>
> Key: ZEPPELIN-9
> URL: https://issues.apache.org/jira/browse/ZEPPELIN-9
> Project: Zeppelin
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.5.0
> Reporter: RJ Nowling
> Priority: Minor
>
> The Spark profiles in the maven pom track the latest minor releases for each Spark branch (1.1.x, 1.2.x, 1.3.x). I had trouble running Zeppelin compiled with Spark 1.2.1 against a cluster running Spark 1.2.0, however, suggesting that the 1.2.x releases are not necessarily binary compatible.
> As a result, I suggest that the Spark profiles be to incorporate the minor number. Specifically, changing from spark-1.1, spark-1.2, and spark-1.3 to spark-1.1.0, spark-1.1.1, spark-1.2.0, spark-1.2.1, and spark-1.3.0
> I'd be happy to provide patch if others agree to this change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)