[
https://issues.apache.org/jira/browse/HBASE-26512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated HBASE-26512:
--------------------------------
Release Note: HBASE-23930 changed the formatting of the timestamp attribute
on each Cell as displayed by the HBase shell to be formatted as an ISO-8601
string rather that milliseconds since the epoch. Some users may have logic
which expects the timestamp to be displayed as milliseconds since the epoch.
This change introduces the configuration property
hbase.shell.timestamp.format.epoch which controls whether the shell will print
an ISO-8601 formatted timestamp (the default "false") or milliseconds since the
epoch ("true"). (was: HBASE-23930 changed the formatting of the timestamp
attribute on each Cell as displayed by the HBase shell to be formatted as an
ISO-8601 string rather that milliseconds since the epoch. Some users may have
logic which expects the timestamp to be displayed as milliseconds since the
epoch. This change introduces the configuration property
hbase.shell.timestamp.format.epoch which controls whether the shell will print
an ISO-8601 formatted timestamp (the default "true") or milliseconds since the
epoch ("false").)
> 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)
