Sorry, if I misinterpreted your actions/comments. I was lead to believe
that you didn't consider this a problem that we should tackle prior to
2.0 (setting fixVersion=2.0, citing "unable to do this prior to 2.0", etc)
On 12/4/17 10:41 PM, Christopher wrote:
I'm not certain what I'm supposed to be in disagreement with. I think
you've presented a fair assessment of the situation, and I agree with the
severity of the issue.
The only other path I can see would be to not have a "bridge" version at
all and instead require upgrading Accumulo simultaneously with Hadoop. I
kind of like that option, but I don't think it's realistic for our
audiences, as it doesn't allow them to manage their upgrade risks, so the
shaded "bridge" version seems like the better option.
On Mon, Dec 4, 2017 at 6:19 PM Josh Elser<els...@apache.org> wrote:
This is a severe enough problem to me that I would consider breaking API
compatibility and fixing the API leak in 1.7/1.8. I'm curious what
people other than Christopher think (assuming from his comments/JIRA
work that he disagrees with me).
