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 1BD1317933 for ; Tue, 17 Feb 2015 07:06:18 +0000 (UTC) Received: (qmail 82528 invoked by uid 500); 17 Feb 2015 07:06:11 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 82487 invoked by uid 500); 17 Feb 2015 07:06:11 -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 82472 invoked by uid 99); 17 Feb 2015 07:06:11 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2015 07:06:11 +0000 Date: Tue, 17 Feb 2015 07:06:11 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs reopened ACCUMULO-3386: ----------------------------------------- > 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 > Assignee: Corey J. Nolet > 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 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)