[
https://issues.apache.org/jira/browse/ACCUMULO-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490941#comment-13490941
]
John Vines commented on ACCUMULO-776:
-------------------------------------
I don't think it's that painful. Looking at the removed lines of the patch, it
looks like the formatted date string was stored, which included the time zone
info. If we just make the new system a Stringified long, with the assumption
that everything is GMT (as enforced by the code), then we can handle backward
compatibility for any entires that have non-digit characters in it.
But yes, I think you bring up a larger question of what date 253402300800001 is
supposed to be. That's either microsecond based time or it's past 10,000 AD.
While I have faith in our software, I'm not sure if humanity will be around
that long...
> TimestampFilter should serialize start and end as longs in the IteratorSetting
> ------------------------------------------------------------------------------
>
> Key: ACCUMULO-776
> URL: https://issues.apache.org/jira/browse/ACCUMULO-776
> 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: http://www.atlassian.com/software/jira
