[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003346#comment-14003346 ] Hudson commented on HBASE-6990: --- FAILURE: Integrated in hbase-0.96 #399 (See [https://builds.apache.org/job/hbase-0.96/399/]) HBASE-6990 ADDENDUM (jmhsieh: rev 1595410) * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/util/PrettyPrinter.java HBASE-6990 pretty print TTL (Esteban Gutierrez) (jmhsieh: rev 1595395) * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/branches/0.96/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 Fix For: 0.99.0, 0.96.3, 0.98.3 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002139#comment-14002139 ] Andrew Purtell commented on HBASE-6990: --- Belated +1, nice change 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 Fix For: 0.99.0, 0.96.3, 0.98.3 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001105#comment-14001105 ] Hudson commented on HBASE-6990: --- SUCCESS: Integrated in HBase-0.98 #307 (See [https://builds.apache.org/job/HBase-0.98/307/]) HBASE-6990 ADDENDUM (jmhsieh: rev 1595408) * /hbase/branches/0.98/hbase-common/src/main/java/org/apache/hadoop/hbase/util/PrettyPrinter.java HBASE-6990 pretty print TTL (Esteban Gutierrez) (jmhsieh: rev 1595397) * /hbase/branches/0.98/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/branches/0.98/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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001240#comment-14001240 ] Esteban Gutierrez commented on HBASE-6990: -- [~lhofhansl] I think is just a nice to have, but not a critical thing. 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 Fix For: 0.99.0, 0.96.3, 0.98.3 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000763#comment-14000763 ] Hudson commented on HBASE-6990: --- FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #291 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/291/]) HBASE-6990 ADDENDUM (jmhsieh: rev 1595408) * /hbase/branches/0.98/hbase-common/src/main/java/org/apache/hadoop/hbase/util/PrettyPrinter.java HBASE-6990 pretty print TTL (Esteban Gutierrez) (jmhsieh: rev 1595397) * /hbase/branches/0.98/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/branches/0.98/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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001004#comment-14001004 ] Lars Hofhansl commented on HBASE-6990: -- Do you want this in 0.94, [~esteban]? It seems mostly like a nice to have. Is there a strong reason to have this in 0.94? 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997894#comment-13997894 ] Esteban Gutierrez commented on HBASE-6990: -- Sorry [~stacke], this was meant for [~stack] Apache JIRA is acting slow. 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000440#comment-14000440 ] Jean-Daniel Cryans commented on HBASE-6990: --- That representation is pretty much my original ask, +1 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999467#comment-13999467
]
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/12644729/HBASE-6990.v3.patch
against trunk revision .
ATTACHMENT ID: 12644729
{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:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
58 warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.io.hfile.TestScannerSelectionUsingKeyRange
org.apache.hadoop.hbase.master.TestCatalogJanitor
org.apache.hadoop.hbase.regionserver.TestBlocksScanned
org.apache.hadoop.hbase.regionserver.TestResettingCounters
org.apache.hadoop.hbase.procedure.TestProcedureManager
org.apache.hadoop.hbase.regionserver.TestScanWithBloomError
org.apache.hadoop.hbase.regionserver.TestColumnSeeking
org.apache.hadoop.hbase.regionserver.TestSplitTransaction
org.apache.hadoop.hbase.filter.TestColumnPrefixFilter
org.apache.hadoop.hbase.regionserver.TestDefaultCompactSelection
org.apache.hadoop.hbase.client.TestIntraRowPagination
org.apache.hadoop.hbase.filter.TestDependentColumnFilter
org.apache.hadoop.hbase.coprocessor.TestRegionObserverStacking
org.apache.hadoop.hbase.regionserver.TestHRegionInfo
org.apache.hadoop.hbase.filter.TestInvocationRecordFilter
org.apache.hadoop.hbase.filter.TestMultipleColumnPrefixFilter
org.apache.hadoop.hbase.snapshot.TestRestoreSnapshotHelper
org.apache.hadoop.hbase.regionserver.TestKeepDeletes
org.apache.hadoop.hbase.regionserver.TestMinVersions
org.apache.hadoop.hbase.filter.TestFilter
org.apache.hadoop.hbase.regionserver.TestScanner
org.apache.hadoop.hbase.regionserver.TestWideScanner
org.apache.hadoop.hbase.regionserver.TestRegionMergeTransaction
org.apache.hadoop.hbase.coprocessor.TestCoprocessorInterface
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9518//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
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000558#comment-14000558 ] Jonathan Hsieh commented on HBASE-6990: --- commited to trunk, 0.98 and 0.96. Thanks esteban et al! 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000575#comment-14000575 ] Jeffrey Zhong commented on HBASE-6990: -- Have we committed PrettyPrinter.java? Thanks. 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998015#comment-13998015
]
Esteban Gutierrez commented on HBASE-6990:
--
It should be: {{259206 SECONDS (3 DAYS)}} I had a prototype what would
basically do correctly {{3 DAYS 3 SECONDS}} version but I think just having
this approximate number of days and the true value in seconds should be fine. I
could add the word {{APPROXIMATELY}} if !(TTL % DAY_IN_SECONDS).
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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998421#comment-13998421 ] stack commented on HBASE-6990: -- How hard to do 3 days and 3 seconds? That seems better than shoving an APPROXIMATELY in there. This is a great patch BTW. Should save fellas some headache 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 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997829#comment-13997829
]
Jonathan Hsieh commented on HBASE-6990:
---
Here's the example from the unit test. Are you looking for more than that
[~stack]?
{code}
+ @Test
+ public void testPrettyPrinterTTL() {
+String out;
+Long[] values =
+ { 0L, 1L, 1000L, 86400L, 259200L, Long.valueOf(Integer.MAX_VALUE) };
+String[] messages =
+ { 0 SECONDS, 1 SECOND, 1000 SECONDS, 86400 SECONDS (1 DAY),
+259200 SECONDS (3 DAYS), FOREVER };
+
+for (int i = 0; i values.length; i++) {
+ out = PrettyPrinter.format(Long.toString(values[i]),
HColumnDescriptor.getUnit(
+ HColumnDescriptor.TTL));
+ assertEquals(
+ String.format(
+ Expected %s , messages[i]), messages[i], out);
+}
+ }
{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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997844#comment-13997844 ] stack commented on HBASE-6990: -- Thanks. I was wondering how it looked in context, in the shell. What does it look like when the time is 259203: i.e. 3 seconds greater than 3 days? 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992737#comment-13992737
]
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/12643908/HBASE-6990.v1.patch
against trunk revision .
ATTACHMENT ID: 12643908
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9482//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
Reporter: Jean-Daniel Cryans
Assignee: Esteban Gutierrez
Priority: Minor
Attachments: HBASE-6990.v0.patch, HBASE-6990.v1.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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997791#comment-13997791 ] stack commented on HBASE-6990: -- Mighty [~esteban], any examples of what the new pretty print looks like (for those of us wi/ little by way of imagination)! 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997946#comment-13997946 ] stack commented on HBASE-6990: -- That looks good Esteban. What does it look like when the time is 259203: i.e. 3 seconds greater than 3 days? 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996526#comment-13996526
]
Jonathan Hsieh commented on HBASE-6990:
---
Let's make this super readable and so we can use this for other units
eventually as well. A bunch of terms are added and we can probably get away
with fewer.
Human is a poor class name (the code in it doesn't represent a human).
Maybe PrettyPrinter?
Unit is good to have in pretty printer.
Keep the HColumnDescriptor stuff in HCD, and keep the PrettyPrinter stuff in
its class. So move getUnit, the method that figure out units, into
HColumnDescriptor (e.g. TTL is a TIME_INTERVAL unit) . Have the
Human.toHumanString call take the value and the unit and not the HCD specific
string. It would look like Human.toHumanString(String value, Unit unit).
nit: Rename toHumanString to something else like format. So the call HCD
might become PrettyPrinter.format(value, unit). Seems clearer than
Human.toHumanString.
Duplicate? its in the Human class also.
{code}
/**
+ * TTL related constat for human readable representation
+ */
+
+ public static final Long SECONDS_PER_DAY = 60 * 60 * 24L;
+
+
+ /**
{code}
TTL is only related to column descriptor. I'm suprised there is no constant for
that elsewhere?
{code}
+ /**
+ * TTL related constants for human readable representation
+ */
+ public static final Long SECONDS_PER_DAY = 60 * 60 * 24L;
+ public static final String TTL = TTL;
+
{code}
Also consider passing in the string buffer instead of creating a new one in
each of the helper methods.
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
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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994543#comment-13994543
]
Jonathan Hsieh commented on HBASE-6990:
---
Please add tests.
Please check the find bugs and report if this patch added it.
I don't think the toHuman function or enum should live in HColumnDescriptor.
Move it to o.a.h.h.util.
Can make this more readable as:
{code}
//+ public static final Long SECONDS_PER_DAY = 86400L;
+ public static final Long SECONDS_PER_DAY = 60 * 60 * 24; // secs * minutes *
hours
{code}
So this is going to print total seconds and then total days? Why print
something like 3d 4h 15s? I don't think you need Math.floor.
{code}
+if (interval = SECONDS_PER_DAY) {
+ sb.append(interval);
+ sb.append( SECONDS ();
+ sb.append((int) Math.floor(interval/SECONDS_PER_DAY));
+ sb.append( DAY + (interval == SECONDS_PER_DAY ? : S));
+ sb.append());
+}
{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
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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954330#comment-13954330 ] Jonathan Hsieh commented on HBASE-6990: --- [~esteban], it's been nearly a year with no response so I think it is safe for you to grab it. I'll just assign it to you. Pretty print TTL Key: HBASE-6990 URL: https://issues.apache.org/jira/browse/HBASE-6990 Project: HBase Issue Type: Improvement Affects Versions: 0.94.6, 0.95.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Priority: Minor 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13951550#comment-13951550 ] Esteban Gutierrez commented on HBASE-6990: -- [~kevin.odell] Ping, are you working on this? Pretty print TTL Key: HBASE-6990 URL: https://issues.apache.org/jira/browse/HBASE-6990 Project: HBase Issue Type: Improvement Affects Versions: 0.94.6, 0.95.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Priority: Minor 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 7776 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)
[jira] [Commented] (HBASE-6990) Pretty print TTL
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13648738#comment-13648738 ] Jean-Daniel Cryans commented on HBASE-6990: --- [~kevin.odell], still planning on fixing this? Pretty print TTL Key: HBASE-6990 URL: https://issues.apache.org/jira/browse/HBASE-6990 Project: HBase Issue Type: Improvement Affects Versions: 0.94.6, 0.95.0 Reporter: Jean-Daniel Cryans Assignee: Kevin Odell Priority: Minor 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 7776 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
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 7776 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
[
https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507540#comment-13507540
]
Jean-Daniel Cryans commented on HBASE-6990:
---
[~cody.mar...@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 7776 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
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 7776 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
[ https://issues.apache.org/jira/browse/HBASE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 7776 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
