[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000659#comment-14000659
]
Hudson commented on HBASE-6990:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK #5133 (See
[https://builds.apache.org/job/HBase-TRUNK/5133/])
HBASE-6990 ADDENDUM (jmhsieh: rev 1595409)
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/PrettyPrinter.java
HBASE-6990 pretty print TTL (Esteban Gutierrez) (jmhsieh: rev 1595396)
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
> Pretty print TTL
> ----------------
>
> Key: HBASE-6990
> URL: https://issues.apache.org/jira/browse/HBASE-6990
> Project: HBase
> Issue Type: Improvement
> Components: Usability
> 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, HBASE-6990.v4.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)
