[ https://issues.apache.org/jira/browse/SPARK-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197163#comment-15197163 ]
Sean Owen commented on SPARK-13933: ----------------------------------- The curator update itself seems fine but the Guava thing is unfortunate. So we'd have to depend on a custom Guava build? Is there an actual problem to not updating the curator dep -- if they're API compatible it shouldn't matter really. > hadoop-2.7 profile's curator version should be 2.7.1 > ---------------------------------------------------- > > Key: SPARK-13933 > URL: https://issues.apache.org/jira/browse/SPARK-13933 > Project: Spark > Issue Type: Bug > Components: Build > Affects Versions: 2.0.0 > Reporter: Steve Loughran > Priority: Minor > > This is pretty minor, more due diligence than any binary compatibility. > # the {{hadoop-2.7}} profile declares the curator version to be 2.6.0 > # the actual hadoop-2.7.1 dependency is of curator 2.7.1; this came from > HADOOP-11492 > For consistency, the profile can/should be changed. However, note that as > well as some incompatibilities defined in HADOOP-11492; the version of Guava > that curator asserts a need for is 15.x. HADOOP-11612 showed what needed to > be done to address compatibility problems there; one of the Curator classes > had to be forked to make compatible with guava 11+ -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org