[
https://issues.apache.org/jira/browse/HBASE-26512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452195#comment-17452195
]
Istvan Toth commented on HBASE-26512:
-------------------------------------
[~anoop.hbase]
True is the HBase 2.2 behaviour.
False is the HBase 2.3/2.4 behaviour.
This patch does nothing if you don't set the new property explictily to true.
Default=True would revert the default behaviour to the HBase 2.2 format,
changing the default timestamp format once again.
I don't think we want that.
> Make timestamp format configurable in HBase shell scan output
> -------------------------------------------------------------
>
> Key: HBASE-26512
> URL: https://issues.apache.org/jira/browse/HBASE-26512
> Project: HBase
> Issue Type: Improvement
> Components: shell
> Affects Versions: 3.0.0-alpha-1
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.9
>
>
> HBASE-23930 and HBASE-24937 has changed the timestamp format shown in scan
> results in HBase shells.
> This may break existing use cases that use hbase shell as a client. (as
> opposed to the java, rest, or thrift APIs)
> I propose adding a configuration option to make it configurable.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
