[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000926#comment-14000926
]
Hadoop QA commented on HBASE-6990:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645173/HBASE-6990.v4.patch
against trunk revision .
ATTACHMENT ID: 12645173
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9536//console
This message is automatically generated.
> 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)
