Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 25 Mar 2013 20:39:15 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12638949.1364238655888.51078.1364243955965@arcas>
In-Reply-To: <JIRA.12638949.1364238655888@arcas>
References: <JIRA.12638949.1364238655888@arcas>
Subject: [jira] [Commented] (ACCUMULO-1203) add option to scan command to
 display dateString
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613091#comment-13613091 ] 

Josh Elser commented on ACCUMULO-1203:
--------------------------------------

[~kevin.faro] how do you feel about adding a formatter which formats the Long as the readable date string?

At an initial glance, it seems to me that adding the option to `scan` overlaps a little with what the Formatters were intended to do.

But, the next line of thought would be the ability to stack Formatters. Although, an easy workaround would to make an extension point from DefaultFormatter which does the long->String change and then users could extend it when they have custom Formatters. Thoughts?
                
> add option to scan command to display dateString
> ------------------------------------------------
>
>                 Key: ACCUMULO-1203
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1203
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: shell
>            Reporter: Kevin Faro
>            Assignee: Kevin Faro
>            Priority: Minor
>         Attachments: ACCUMULO-1203.patch
>
>
> When I was trying to debug my SummingArrayCombiner, I figured it would have been helpful to display the dateString vs just the long representation.

--
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