accumulo-notifications mailing list archives

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

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

Josh Elser commented on ACCUMULO-1581:
--------------------------------------

{{Key.toString()}} invokes [appendPrintableString|https://github.com/apache/accumulo/blob/master/core/src/main/java/org/apache/accumulo/core/data/Key.java#L769]
which truncates each element of the Key (e.g. row, colfam, etc) before it gets printed.

Again, the intent here is *not* to limit the number of results returned by the {{listscans}}
command, it is to limit the *printout of the iterator options* for each running scan. The
{{ScanCommand}} class is not relevant here, you should be looking at the {{ListScansCommand}}
class, specifically the {{ActiveScanIterator}} class which is referenced by the {{ListScansCommand}}.
In there, you can see the "ITERATOR OPTIONS" header -- this is the column that should be truncated
to account for excessive length.

After implementing this, it would be good to also add an option to the {{ListScansCommand}}
that will revert it back to how it operates now (to ensure users can still view all of the
data if they so choose).

> 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