You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Aaron Cordova <aa...@koverse.com> on 2013/11/06 06:56:49 UTC
Accumulo-1379
I see that 1379 affects 1.4.3 and it looks like it’s being fixed for 1.6.0.
Was this by any chance fixed in 1.4.4 or somehow not apply?
Thanks,
Aaron
Re: Accumulo-1379
Posted by Aaron Cordova <aa...@cordovas.org>.
I’ll file a ticket. If Sean fixes it I’d happily review.
On Nov 6, 2013, at 4:49 PM, Christopher <ct...@apache.org> wrote:
> +1 to to backport the bugfix.
>
> To David 'Helpful Links' Medinets:
> https://chrome.google.com/webstore/detail/goto-bug-for-jira/ocjecccldncbghkfbplmopcgafnfffoc
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Wed, Nov 6, 2013 at 11:23 AM, Joey Echeverria
> <jo...@clouderagovt.com> wrote:
>> I'm with Sean, we should file new JIRAs to backport the fix.
>>
>> -Joey
>>
>>
>> On Wed, Nov 6, 2013 at 9:39 AM, Sean Busbey <bu...@cloudera.com> wrote:
>>> On Tue, Nov 5, 2013 at 11:56 PM, Aaron Cordova <aa...@koverse.com>wrote:
>>>
>>>> I see that 1379 affects 1.4.3 and it looks like it’s being fixed for 1.6.0.
>>>>
>>>> Was this by any chance fixed in 1.4.4 or somehow not apply?
>>>>
>>>>
>>>>
>>> AFAICT, it only got fixed in master. I don't see anything in the related
>>> commits that breaks compatibility.
>>>
>>> If you can file a ticket and handle a review, I'd be happy to do the
>>> backporting to 1.4.x and 1.5.x.
>>>
>>>
>>> --
>>> Sean
Re: Accumulo-1379
Posted by Christopher <ct...@apache.org>.
+1 to to backport the bugfix.
To David 'Helpful Links' Medinets:
https://chrome.google.com/webstore/detail/goto-bug-for-jira/ocjecccldncbghkfbplmopcgafnfffoc
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Wed, Nov 6, 2013 at 11:23 AM, Joey Echeverria
<jo...@clouderagovt.com> wrote:
> I'm with Sean, we should file new JIRAs to backport the fix.
>
> -Joey
>
>
> On Wed, Nov 6, 2013 at 9:39 AM, Sean Busbey <bu...@cloudera.com> wrote:
>> On Tue, Nov 5, 2013 at 11:56 PM, Aaron Cordova <aa...@koverse.com>wrote:
>>
>>> I see that 1379 affects 1.4.3 and it looks like it’s being fixed for 1.6.0.
>>>
>>> Was this by any chance fixed in 1.4.4 or somehow not apply?
>>>
>>>
>>>
>> AFAICT, it only got fixed in master. I don't see anything in the related
>> commits that breaks compatibility.
>>
>> If you can file a ticket and handle a review, I'd be happy to do the
>> backporting to 1.4.x and 1.5.x.
>>
>>
>> --
>> Sean
Re: Accumulo-1379
Posted by Joey Echeverria <jo...@clouderagovt.com>.
I'm with Sean, we should file new JIRAs to backport the fix.
-Joey
On Wed, Nov 6, 2013 at 9:39 AM, Sean Busbey <bu...@cloudera.com> wrote:
> On Tue, Nov 5, 2013 at 11:56 PM, Aaron Cordova <aa...@koverse.com>wrote:
>
>> I see that 1379 affects 1.4.3 and it looks like it’s being fixed for 1.6.0.
>>
>> Was this by any chance fixed in 1.4.4 or somehow not apply?
>>
>>
>>
> AFAICT, it only got fixed in master. I don't see anything in the related
> commits that breaks compatibility.
>
> If you can file a ticket and handle a review, I'd be happy to do the
> backporting to 1.4.x and 1.5.x.
>
>
> --
> Sean
Re: Accumulo-1379
Posted by David Medinets <da...@gmail.com>.
https://issues.apache.org/jira/browse/ACCUMULO-1379
- David 'Helpful Links' Medinets
On Wed, Nov 6, 2013 at 9:39 AM, Sean Busbey <bu...@cloudera.com> wrote:
> On Tue, Nov 5, 2013 at 11:56 PM, Aaron Cordova <aaroncordova@koverse.com
> >wrote:
>
> > I see that 1379 affects 1.4.3 and it looks like it’s being fixed for
> 1.6.0.
> >
> > Was this by any chance fixed in 1.4.4 or somehow not apply?
> >
> >
> >
> AFAICT, it only got fixed in master. I don't see anything in the related
> commits that breaks compatibility.
>
> If you can file a ticket and handle a review, I'd be happy to do the
> backporting to 1.4.x and 1.5.x.
>
>
> --
> Sean
>
Re: Accumulo-1379
Posted by Sean Busbey <bu...@cloudera.com>.
On Tue, Nov 5, 2013 at 11:56 PM, Aaron Cordova <aa...@koverse.com>wrote:
> I see that 1379 affects 1.4.3 and it looks like it’s being fixed for 1.6.0.
>
> Was this by any chance fixed in 1.4.4 or somehow not apply?
>
>
>
AFAICT, it only got fixed in master. I don't see anything in the related
commits that breaks compatibility.
If you can file a ticket and handle a review, I'd be happy to do the
backporting to 1.4.x and 1.5.x.
--
Sean