Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 31D7F956C for ; Tue, 6 Nov 2012 02:12:14 +0000 (UTC) Received: (qmail 52226 invoked by uid 500); 6 Nov 2012 02:12:14 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 52176 invoked by uid 500); 6 Nov 2012 02:12:14 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 52166 invoked by uid 99); 6 Nov 2012 02:12:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2012 02:12:14 +0000 Date: Tue, 6 Nov 2012 02:12:13 +0000 (UTC) From: "John Vines (JIRA)" To: notifications@accumulo.apache.org Message-ID: <1579590441.71936.1352167934050.JavaMail.jiratomcat@arcas> In-Reply-To: <1491103439.129303.1348681148637.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (ACCUMULO-776) TimestampFilter should serialize start and end as longs in the IteratorSetting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491122#comment-13491122 ] John Vines commented on ACCUMULO-776: ------------------------------------- Interesting, that's a neat application of the visibilities. I looked over the patch again, and I'm wondering if we have a compatability issue after all. I don't think anything is being changed in how things are being stored in ZK. So the only issue is the wire compatability which Keith mentioned before, which is nowhere as severe of an issue IMO. > 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