Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 5 Dec 2014 22:02:12 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12759897.1417816903000.88780.1417816932307@Atlassian.JIRA>
In-Reply-To: <JIRA.12759897.1417816903000@Atlassian.JIRA>
References: <JIRA.12759897.1417816903000@Atlassian.JIRA>
 <JIRA.12759897.1417816903644@arcas>
Subject: [jira] [Created] (ACCUMULO-3386) Update release notes to explain
 how to correct data written with the buggy DateLexicoder
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Christopher Tubbs created ACCUMULO-3386:
-------------------------------------------

             Summary: Update release notes to explain how to correct data written with the buggy DateLexicoder
                 Key: ACCUMULO-3386
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3386
             Project: Accumulo
          Issue Type: Sub-task
            Reporter: Christopher Tubbs
            Priority: Blocker
             Fix For: 1.6.2, 1.7.0


We should make sure users who may have used the buggy DateLexicoder are informed of a method which they can use to correct their data or to continue using the old behavior.

To read data with the old, broken behavior (if needed):
{code}
Lexicoder lex = new ULongLexicoder();
for (Entry<Key, Value> e : scanner) {
  Date d = new Date(lex.decode(TextUtil.getBytes(e.getKey().getRow())));
  // ...
}
{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)