[
https://issues.apache.org/jira/browse/ACCUMULO-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490955#comment-13490955
]
Keith Turner commented on ACCUMULO-776:
---------------------------------------
I suppose we can serialize the new persistent format however we want. For
example we could prefix it with LONG inorder to preclude any ambiguity with the
old persistent format. We could also use a different option name, but then
would need to handle the case where the old and new option exists. So to
simplify I would rather the current option support two different persistent
formats.
> 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
