[
https://issues.apache.org/jira/browse/HBASE-26512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453063#comment-17453063
]
Josh Elser commented on HBASE-26512:
------------------------------------
{quote}On a patch version 2.4.9 and minor version 2.5.0, we wanted to change
the behave? Why not keep the default value of the new config to true?
{quote}
{quote}This patch does nothing if you don't set the new property explictily to
true.
{quote}
Exactly. When I tested this locally, I made sure that it does not change the
semantics of how 2.4/2.5 work today. If you change the config, then you restore
the old 2.2 way of rendering timestamps (if that's something you care about as
a user). Works how you expect it to, Anoop :)
> 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)
