[
https://issues.apache.org/jira/browse/HBASE-26512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450410#comment-17450410
]
Istvan Toth commented on HBASE-26512:
-------------------------------------
manual testing:
with *hbase.shell.timestamp.format.epoch* set to true:
{noformat}
hbase:001:0> scan 'test'
ROW COLUMN+CELL
row1 column=cf:a,
timestamp=1638186162954, value=value1
1 row(s)
Took 0.1315 seconds
{noformat}
the default:
{noformat}
hbase:001:0> scan 'test'
ROW COLUMN+CELL
row1 column=cf:a,
timestamp=2021-11-29T12:42:42.954, value=value1
1 row(s)
Took 0.1388 seconds
{noformat}
> 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: Bug
> Components: shell
> Affects Versions: 3.0.0-alpha-1
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> 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)
