accumulo-notifications mailing list archives

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


Keith Turner commented on ACCUMULO-3402:

[~elserj] Can you please explain the rational behind your shift in thinking?  At one point
you said the following, the switched to option 1.  Basically can someone please ELI5 what
the big win for users is for having a seperate M/R module?  Lets call moving everything back
to core option 3.

bq. FWIW, the easiest resolution I can come up with short-term is a revert of the original
changes (move the classes back to core/) and come up with a better solution moving forward.

There is possibly an option 4.  Break core into two modules core-mr and core-foo (not sure
what to call it).  Make the current core module depend on the two new modules.  I don't really
like option 4, but if there is some strong reason to put the MR code in its own module, option
4 may still maintain 1.6 pom compatability from a users perspective.

[~elserj] and [~ctubbsii] it seems like you guys are leaning twoards option 1.  I don't like
this idea of deprecating the entire map reduce API because of historical churn in MR API.
 This churn occurred in 1.4, 1.5, and 1.6 see ACCUMULO-1533 (removed a lot of deprecated stuff
in MR API), ACCUMULO-769, ACCUMULO-267.   Of course as I said I don't understand what the
win for users is w/ moving stuff into a seperate module, and that lack of knowledge makes
me dislike option 1.

> 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