accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Ridley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1581) Limit length of values printed in listscans by default
Date Mon, 28 Apr 2014 14:46:17 GMT

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

Michael Ridley commented on ACCUMULO-1581:
------------------------------------------

[~elserj] I think I may be muddling the issue in ways I didn't mean to by mentioning {{ScanCommand}}.
 I only meant to reference it in the sense that I wanted the {{LIstScansCommand}} to have
similar semantics.  The functionality in this JIRA is definitely implemented in {{ListScansCommand}}
and {{ActiveScanIterator}}.  Sorry for any confusion on that.

> Limit length of values printed in listscans by default
> ------------------------------------------------------
>
>                 Key: ACCUMULO-1581
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1581
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: shell
>            Reporter: Josh Elser
>              Labels: newbie
>             Fix For: 1.7.0
>
>
> Listscans currently print out the entire options map provided to a ScanSession. If these
large option values are printed, it makes the output rather difficult to read/parse.
> We should add an upper limit to the length of the key-values printed out from said option
map, including a "<TRUNCATED>" to match what is done for large Keys when scanning a
table. We could also add an option to override the truncation for when people really want
to see the complete option map.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message