[
https://issues.apache.org/jira/browse/HBASE-18920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187290#comment-16187290
]
James Taylor commented on HBASE-18920:
--------------------------------------
IMHO, there are two changes needed:
- 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.
- Making it configurable would be nice, but there are so many dials and knobs,
it's unlikely someone will modify it.
I just filed it because I spent a fair amount of time debugging a non issue,
thinking Phoenix wasn't projecting all the expected column qualifiers (and I'd
rather save others this pain).
> 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
(v6.4.14#64029)
