accumulo-notifications mailing list archives

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


Josh Elser commented on ACCUMULO-3402:

bq. I like option 1).

Ditto, that's what I'm leaning towards as well. It's less abrupt than reverting the old commits
and kepts backwards compatibility.

bq. (without comment on if a dependency coordinate change should be considered breaking)

And just to address this, yes, I know this is currently unhandled by any accepted practices
that we have for Accumulo, but I believe the breakage that we create by doing this is quite
real and obvious. Please start a thread on dev if you'd like to discuss this further and we
work through the issue there.

> 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