[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997892#comment-13997892
]
Esteban Gutierrez commented on HBASE-6990:
------------------------------------------
[~stacke]
{code}
hbase(main):002:0> create 'sample', {NAME => 'cf', TTL => '259203'}
base(main):003:0> describe 'sample'
DESCRIPTION
ENABLED
'sample', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'ROW',
REPLICATION_SCOPE => '0', VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIONS
=> '0' true
, TTL => '259203 SECONDS (3 DAYS)', KEEP_DELETED_CELLS => 'false', BLOCKSIZE
=> '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'}
1 row(s) in 0.0590 seconds
{code}
> Pretty print TTL
> ----------------
>
> Key: HBASE-6990
> URL: https://issues.apache.org/jira/browse/HBASE-6990
> Project: HBase
> Issue Type: Improvement
> Reporter: Jean-Daniel Cryans
> Assignee: Esteban Gutierrez
> Priority: Minor
> Attachments: HBASE-6990.v0.patch, HBASE-6990.v1.patch,
> HBASE-6990.v2.patch, HBASE-6990.v3.patch
>
>
> I've seen a lot of users getting confused by the TTL configuration and I
> think that if we just pretty printed it it would solve most of the issues.
> For example, let's say a user wanted to set a TTL of 90 days. That would be
> 7776000. But let's say that it was typo'd to 77760000 instead, it gives you
> 900 days!
> So when we print the TTL we could do something like "x days, x hours, x
> minutes, x seconds (real_ttl_value)". This would also help people when they
> use ms instead of seconds as they would see really big values in there.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
