hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18920) Operation.toString() is counterintuitive
Date Sun, 01 Oct 2017 09:29:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187321#comment-16187321

Chia-Ping Tsai commented on HBASE-18920:

Indicate that there are more column qualifiers projected when you've truncated the toString()
based on the max number to display. Something simple like adding a "..." to the string would
be fine.
Increasing the default value to something like 20 or 30. That won't be an issue memory-wise,
but will handle more cases out of the box.
+1. Do you start the patch?

> Operation.toString() is counterintuitive
> ----------------------------------------
>                 Key: HBASE-18920
>                 URL: https://issues.apache.org/jira/browse/HBASE-18920
>             Project: HBase
>          Issue Type: Bug
>            Reporter: James Taylor
> When debugging, you often need to know which columns are projected into the Scan. The
Operation.toString() silently truncates what you see to the first 5. Typically, if you truncate
a value, you should end it with "..." so that the user knows there are actually more (instead
of wasting time thinking they're not projecting everything that needs to be projected). Also,
a limit of 5 is way to small of a default.

This message was sent by Atlassian JIRA

View raw message