accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-776) TimestampFilter should serialize start and end as longs in the IteratorSetting
Date Mon, 05 Nov 2012 20:44:12 GMT


John Vines commented on ACCUMULO-776:

I'm concerned about the implications of the transition, regardless of version. Not having
viewed, does this patch handle backwards compatability?

On a higher level about this ticket though, one of the reasons we used a formated Date is
to prevent issues of clients and servers being in different timezone configurations, particularly
the client and the actual server. Again, not having viewed the patch, I do not know if there
is anything done here to handle it, but there needs to be some sort of consideration here.
> TimestampFilter should serialize start and end as longs in the IteratorSetting
> ------------------------------------------------------------------------------
>                 Key: ACCUMULO-776
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Marcio Silva
>            Assignee: Billie Rinaldi
>            Priority: Minor
>         Attachments: ACCUMULO-776.patch
> Although the TimestampFilter supports using longs to set the start or end timestamp,
it formats them as strings using SimpleDateFormat when storing or retrieving them in the IteratorSetting.
> This results in exceptions when the timestamps being used aren't able to be formatted
as _yyyyMMddHHmmssz_. For example, try {{setEnd(253402300800001,true)}}
> Instead, {{setStart()}} and {{setEnd()}} could just as easily use {{String.valueOf(long
i)}} to store the values, and {{init()}} could retrieve them using {{Long.valueOf(String s)}}.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message