accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3402) Introduction of the mapreduce maven module breaks 1.6 compatibility
Date Thu, 11 Dec 2014 23:38:13 GMT

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

Christopher Tubbs commented on ACCUMULO-3402:
---------------------------------------------

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. Now, it seems it is necessary to retain backwards-compatibility, and implementing
option 1 seems to give us that opportunity to follow our convention.

To keep the migration simple, new classes in the new module don't need to include any deprecated
code, and old classes in the old location don't need to include any new code. They can be
copied raw from the 1.6 branch, which ensures quick and easy backwards compatibility without
any fuss.

> Introduction of the mapreduce maven module breaks 1.6 compatibility
> -------------------------------------------------------------------
>
>                 Key: ACCUMULO-3402
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3402
>             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
broken.
> 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
(v6.3.4#6332)

Mime
View raw message