[GitHub] incubator-tephra issue #19: TEPHRA-35 Save compaction state for pruning inva...

2016-11-08 Thread poornachandra
Github user poornachandra commented on the issue: https://github.com/apache/incubator-tephra/pull/19 @anew I'll add the maximum duration check as a separate PR. I'll file a JIRA for it. --- If your project is set up for it, you can reply to this email and have your reply appear on Gi

[GitHub] incubator-tephra issue #19: TEPHRA-35 Save compaction state for pruning inva...

2016-11-07 Thread anew
Github user anew commented on the issue: https://github.com/apache/incubator-tephra/pull/19 @poornachandra are you planning to add this maximum duration as part of this implementation? Or is that a future improvement? --- If your project is set up for it, you can reply to this email

[GitHub] incubator-tephra issue #19: TEPHRA-35 Save compaction state for pruning inva...

2016-11-07 Thread poornachandra
Github user poornachandra commented on the issue: https://github.com/apache/incubator-tephra/pull/19 @anew One way to handle the above issue is to define a time limit that defines a maximum duration a transaction can be used for writing. While doing data writes, we could add some chec

[GitHub] incubator-tephra issue #19: TEPHRA-35 Save compaction state for pruning inva...

2016-11-05 Thread anew
Github user anew commented on the issue: https://github.com/apache/incubator-tephra/pull/19 Question: Suppose I start a transaction, which times out, and therefore goes into the invalid list. A little later HBase performs a major compaction. This transaction and all its writes are rem