You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2012/10/13 02:33:02 UTC
[jira] [Created] (HBASE-6990) Pretty print TTL
Jean-Daniel Cryans created HBASE-6990:
-----------------------------------------
Summary: 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
Priority: Minor
Fix For: 0.92.3, 0.94.3, 0.96.0
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
[jira] [Updated] (HBASE-6990) Pretty print TTL
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-6990:
---------------------------------
Fix Version/s: (was: 0.94.3)
0.94.4
Moving to 0.94.4 unless somebody makes a patch.
> 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
[jira] [Assigned] (HBASE-6990) Pretty print TTL
Posted by "Kevin Odell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Odell reassigned HBASE-6990:
----------------------------------
Assignee: Kevin Odell
> 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.94.3, 0.96.0
>
>
> 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
[jira] [Commented] (HBASE-6990) Pretty print TTL
Posted by "Cody Marcel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507532#comment-13507532 ]
Cody Marcel commented on HBASE-6990:
------------------------------------
Do you know what class this is being logged from? The only place I have found that is logging ttl is TimeToLiveHFileCleaner.
> 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
[jira] [Commented] (HBASE-6990) Pretty print TTL
Posted by "Kevin Odell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476128#comment-13476128 ]
Kevin Odell commented on HBASE-6990:
------------------------------------
+1 - I think this could be extremely helpful.
> 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
> Priority: Minor
> Fix For: 0.92.3, 0.94.3, 0.96.0
>
>
> 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
[jira] [Commented] (HBASE-6990) Pretty print TTL
Posted by "Aditya Kishore (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476647#comment-13476647 ]
Aditya Kishore commented on HBASE-6990:
---------------------------------------
+1.
In addition to interpretation to human readable time format, it would be good if the TTL value = 2147483647 is translated to "Forever" as this is how HBase major compaction will treat it.
> 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.94.3, 0.96.0
>
>
> 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
[jira] [Commented] (HBASE-6990) Pretty print TTL
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ 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