accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3402) Introduction of the mapreduce maven module breaks 1.6 compatibility
Date Fri, 12 Dec 2014 00:25:14 GMT


Mike Drob commented on ACCUMULO-3402:

bq. For what it's worth, it has been our practice to have package names that correspond to
the module. Mapreduce split into its own module didn't do that, because the churn probably
wasn't necessary.
As the one who did this, I'll comment on my intent here. At the time, I believed that MR jobs
written against 1.6 would work just find with a 1.7 instance with the classes split into two
jars. So, we retained runtime compatability (assuming you use {{}} or otherwise include
{{$ACCUMULO_HOME/lib/*}} on your classpath), but I did not realize the impact that this would
have on compilation against future versions.

> Introduction of the mapreduce maven module breaks 1.6 compatibility
> -------------------------------------------------------------------
>                 Key: ACCUMULO-3402
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.7.0
> The introduction of mapreduce maven module breaks backwards compatibility with 1.6.
> Code that previously worked against 1.6 (that used our mapreduce classes) is now broken
without a deprecation cycle -- specifically trying to compile Hive against Accumulo 1.7 is
> While the classes themselves haven't technically changed, the required dependencies have.
In my eyes, this is an incompatible change that violates our current public API rules.

This message was sent by Atlassian JIRA

View raw message