[
https://issues.apache.org/jira/browse/HBASE-30252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092125#comment-18092125
]
guluo commented on HBASE-30252:
-------------------------------
Pushed to all active branches.
Thanks [~liuxiaocs] [~paksyd] for reviewing!
> `hbase snapshot info` display inaccurate snapshot TTL information messages
> --------------------------------------------------------------------------
>
> Key: HBASE-30252
> URL: https://issues.apache.org/jira/browse/HBASE-30252
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Reporter: guluo
> Assignee: guluo
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.5.16, 2.6.7
>
>
> The output as following when executing `./bin/hbase snapshot info
> --list-snapshots`
> {code:java}
> [root@hbase001 hbase-4.0.0-alpha-1-SNAPSHOT]# ./bin/hbase snapshot info
> --list-snapshots
> SNAPSHOT | CREATION TIME | TTL IN SEC | TABLE
> NAME
> 2026-06-23T19:04:18,803 WARN [main] util.NativeCodeLoader: Unable to load
> native-hadoop library for your platform... using builtin-java classes where
> applicable
> 2026-06-23T19:04:18,988 INFO [main] hbase.TableName: Meta table name:
> hbase:meta
> snap_t01 | 2026-06-23T19:03:23 | 0 | t01
> {code}
> The information of TTL is incorrect, what snapshot ttl is 0 means that the
> snapshot never expires in hbase, which should be disaplayed as FOREVER.
> Actually, this is indeed how it is correctly displayed on HBase UI and hbase
> shell
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
