accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Wells <awe...@clearedgeit.com>
Subject Re: Reasoning behind Key(Text row) using Long.MAX_VALUE
Date Fri, 24 Oct 2014 15:43:12 GMT
Also, i just found this: https://issues.apache.org/jira/browse/ACCUMULO-1994

which might be why its currently Long.MAX_VALUE

So maybe a change in the Range implementation, not familiar with Proxy

On Fri, Oct 24, 2014 at 11:36 AM, Andrew Wells <awells@clearedgeit.com>
wrote:

> John, that is probably true too...
>
> On Fri, Oct 24, 2014 at 11:26 AM, Andrew Wells <awells@clearedgeit.com>
> wrote:
>
>> this would be in SNAPSHOT 1.6
>>
>>
>> On Fri, Oct 24, 2014 at 11:08 AM, John Vines <vines@apache.org> wrote:
>>
>>> Makes me think the Range(Text row) constructor should be row, true, row,
>>> false
>>>
>>> On Fri, Oct 24, 2014 at 10:53 AM, Andrew Wells <awells@clearedgeit.com>
>>> wrote:
>>>
>>> > It may be need to change either the implementation of Key::new(Text
>>> row),
>>> > or change the way Range::exact(Text row) matches
>>> >
>>> > Trace on Key::new(Text row)
>>> > line: 102
>>> > line: 75
>>> >
>>> >
>>> > Trace on Range exact(Text row)
>>> > line 656
>>> > line 82
>>> > line 123
>>> >
>>> > This causes Range exact(Text row) to never match
>>> >
>>> >
>>> >
>>> > --
>>> > *Andrew George Wells*
>>> > *Software Engineer*
>>> > *awells@clearedgeit.com <awells@clearedgeit.com>*
>>> >
>>>
>>
>>
>>
>> --
>> *Andrew George Wells*
>> *Software Engineer*
>> *awells@clearedgeit.com <awells@clearedgeit.com>*
>>
>>
>
>
> --
> *Andrew George Wells*
> *Software Engineer*
> *awells@clearedgeit.com <awells@clearedgeit.com>*
>
>


-- 
*Andrew George Wells*
*Software Engineer*
*awells@clearedgeit.com <awells@clearedgeit.com>*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message