[
https://issues.apache.org/jira/browse/ACCUMULO-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490946#comment-13490946
]
Keith Turner commented on ACCUMULO-776:
---------------------------------------
bq. Yikes, does that mean we'd have to include timestamp format conversion for
configured TimestampFilters in our upgrade from 1.4 to 1.5?
This could be done in the TimestampFilter code that reads the config rather
than as part of the upgrade process. I think we can identify the old
persistent format because it ends with alpha chars and distinguish that from
the new format which all numeric chars? Unless there is a completely numeric
timezone?
bq. Did this ticket get opened because someone needed a year >= 10000?
I suppose any long is valid in the timestamp, so the filter should probably
handle it.
> 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
