Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 30 Nov 2012 18:47:58 +0000 (UTC)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <21046427.46176.1354301278633.JavaMail.jiratomcat@arcas>
In-Reply-To: <1414652747.40417.1350088383113.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6990) Pretty print TTL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507540#comment-13507540 ] 

Jean-Daniel Cryans commented on HBASE-6990:
-------------------------------------------

[~cody.marcel@gmail.com] TimeToLiveHFileCleaner is something completely separate, the TTL in question here is the one in HColumnDescriptor. It's being printed as part of {{getValues}}.
                
> Pretty print TTL
> ----------------
>
>                 Key: HBASE-6990
>                 URL: https://issues.apache.org/jira/browse/HBASE-6990
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.92.2, 0.94.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Kevin Odell
>            Priority: Minor
>             Fix For: 0.92.3, 0.96.0, 0.94.4
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira