[jira] [Commented] (PHOENIX-4745) Update Tephra version to 0.14.0-incubating

[ https://issues.apache.org/jira/browse/PHOENIX-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483555#comment-16483555 ] Poorna Chandra commented on PHOENIX-4745: - [~an...@apache.org] The vote for the release was sent

[jira] [Commented] (PHOENIX-4149) Tests using TEPHRA transactional tables flap

[ https://issues.apache.org/jira/browse/PHOENIX-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257864#comment-16257864 ] Poorna Chandra commented on PHOENIX-4149: - [~samarthjain] Looks like the transaction client got

[jira] [Commented] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924868#comment-15924868 ] Poorna Chandra commented on PHOENIX-2993: - In addition to the configuration mentioned in the

[jira] [Comment Edited] (PHOENIX-3585) MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872474#comment-15872474 ] Poorna Chandra edited comment on PHOENIX-3585 at 2/17/17 8:30 PM: --

[jira] [Commented] (PHOENIX-3585) MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872474#comment-15872474 ] Poorna Chandra commented on PHOENIX-3585: - [~tdsilva] Looking at the implementation of

[jira] [Commented] (PHOENIX-3585) MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871192#comment-15871192 ] Poorna Chandra commented on PHOENIX-3585: - Yes - if there is no way to combine the scanner

[jira] [Commented] (PHOENIX-3585) MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868822#comment-15868822 ] Poorna Chandra commented on PHOENIX-3585: - [~tdsilva] Does IndexHalfStoreFileReaderGenerator

[jira] [Commented] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866725#comment-15866725 ] Poorna Chandra commented on PHOENIX-2993: - [~jamestaylor] Tephra 0.11.0-incubating by default

[jira] [Commented] (PHOENIX-3585) MutableIndexIT testSplitDuringIndexScan and testIndexHalfStoreFileReader fail for transactional tables and local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852473#comment-15852473 ] Poorna Chandra commented on PHOENIX-3585: - [~jamestaylor] Looking at the javadocs for the

[jira] [Commented] (PHOENIX-3339) Some transaction tests are flapping under load

[ https://issues.apache.org/jira/browse/PHOENIX-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15719061#comment-15719061 ] Poorna Chandra commented on PHOENIX-3339: - [~jamestaylor] TEPHRA-201 could be the cause for this

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471989#comment-15471989 ] Poorna Chandra commented on PHOENIX-3116: - [~apurtell] Yes, having an errata will help a lot.

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15453895#comment-15453895 ] Poorna Chandra commented on PHOENIX-3116: - If we add reflection for these methods in Tephra

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15453374#comment-15453374 ] Poorna Chandra commented on PHOENIX-3116: - In that case we will have to support it. Should we

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449851#comment-15449851 ] Poorna Chandra commented on PHOENIX-3116: - [~jamestaylor] Do you think those two versions of

[jira] [Commented] (PHOENIX-3116) Upgrade HBase dependency to 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421830#comment-15421830 ] Poorna Chandra commented on PHOENIX-3116: - [~jamestaylor] We have noticed the same thing in CDAP

[jira] [Commented] (PHOENIX-3037) Setup proper security context in compaction/split coprocessor hooks

[ https://issues.apache.org/jira/browse/PHOENIX-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372087#comment-15372087 ] Poorna Chandra commented on PHOENIX-3037: - [~jamestaylor] Thanks for the information. From what

[jira] [Resolved] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Poorna Chandra resolved PHOENIX-2993. - Resolution: Duplicate > Tephra: Prune invalid transaction set once all data for a given

[jira] [Commented] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362039#comment-15362039 ] Poorna Chandra commented on PHOENIX-2993: - Since Tephra JIRA is now available, let's move the

[jira] [Commented] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356256#comment-15356256 ] Poorna Chandra commented on PHOENIX-2993: - bq. What about having the transaction manager track

[jira] [Commented] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343150#comment-15343150 ] Poorna Chandra commented on PHOENIX-2993: - bq. Does HBASE-12859 help you here at all? During a

[jira] [Comment Edited] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342786#comment-15342786 ] Poorna Chandra edited comment on PHOENIX-2993 at 6/22/16 12:44 AM: ---

[jira] [Commented] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342786#comment-15342786 ] Poorna Chandra commented on PHOENIX-2993: - Thanks for the review [~anew] and [~jamestaylor]

[jira] [Updated] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Poorna Chandra updated PHOENIX-2993: Attachment: ApacheTephraAutomaticInvalidListPruning.pdf First cut of design document. I'm

[jira] [Created] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

Poorna Chandra created PHOENIX-2993: --- Summary: Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped Key: PHOENIX-2993 URL:

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308871#comment-15308871 ] Poorna Chandra commented on PHOENIX-2921: - Sorry - missed the earlier comment. In

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297124#comment-15297124 ] Poorna Chandra commented on PHOENIX-2921: - Could it be that class path order is different on

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295384#comment-15295384 ] Poorna Chandra commented on PHOENIX-2921: - [~jamestaylor] How is the classpath for transaction

[jira] [Commented] (PHOENIX-2929) Transactional writes get slow over time due to possible memory leak

[ https://issues.apache.org/jira/browse/PHOENIX-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294447#comment-15294447 ] Poorna Chandra commented on PHOENIX-2929: - Can we get heap dumps of both transaction manager and

[jira] [Commented] (PHOENIX-2929) Transactional writes get slow over time due to possible memory leak

[ https://issues.apache.org/jira/browse/PHOENIX-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294200#comment-15294200 ] Poorna Chandra commented on PHOENIX-2929: - Thanks for reproducing this [~mujtabachohan]. Based

[jira] [Commented] (PHOENIX-2906) Use org.apache.tephra instead of co.cask.tephra

[ https://issues.apache.org/jira/browse/PHOENIX-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292136#comment-15292136 ] Poorna Chandra commented on PHOENIX-2906: - [~jamestaylor] I see some assembly descriptor files

[jira] [Commented] (PHOENIX-2906) Use org.apache.tephra instead of co.cask.tephra

[ https://issues.apache.org/jira/browse/PHOENIX-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291942#comment-15291942 ] Poorna Chandra commented on PHOENIX-2906: - +1 to [~samarthjain]'s suggestion for doing upgrade

[jira] [Commented] (PHOENIX-2670) Guava version incompatibility of Twill vs HBase when launching M/R index

[ https://issues.apache.org/jira/browse/PHOENIX-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15149423#comment-15149423 ] Poorna Chandra commented on PHOENIX-2670: - [~rajeshbabu] Tephra uses Thrift-0.9.0 too -

[jira] [Commented] (PHOENIX-2670) Guava version incompatibility of Twill vs HBase when launching M/R index

[ https://issues.apache.org/jira/browse/PHOENIX-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140240#comment-15140240 ] Poorna Chandra commented on PHOENIX-2670: - [~jamestaylor] We'll try to remove the dependency on

[jira] [Commented] (PHOENIX-2622) Writes to transactional table get slower after regions splits to multiple region servers

[ https://issues.apache.org/jira/browse/PHOENIX-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113252#comment-15113252 ] Poorna Chandra commented on PHOENIX-2622: - Are duplicate ReadFences a problem when adding to

[jira] [Commented] (PHOENIX-2622) Writes to transactional table get slower after regions splits to multiple region servers

[ https://issues.apache.org/jira/browse/PHOENIX-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113454#comment-15113454 ] Poorna Chandra commented on PHOENIX-2622: - I see, cool. > Writes to transactional table get

[jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15109896#comment-15109896 ] Poorna Chandra commented on PHOENIX-2478: - [~mujtabachohan] Can you attach the Tephra

[jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15109602#comment-15109602 ] Poorna Chandra commented on PHOENIX-2478: - [~jamestaylor] The default maximum message size for a

[jira] [Comment Edited] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15109602#comment-15109602 ] Poorna Chandra edited comment on PHOENIX-2478 at 1/20/16 10:48 PM: ---

[jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15109779#comment-15109779 ] Poorna Chandra commented on PHOENIX-2478: - [~mujtabachohan] Other than the warning message, does

[jira] [Commented] (PHOENIX-2608) Incompatibility between Jackson1 version shipped with Phoenix, Yarn

[ https://issues.apache.org/jira/browse/PHOENIX-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106355#comment-15106355 ] Poorna Chandra commented on PHOENIX-2608: - [~jamestaylor] Tephra does not directly depend on

[jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15095006#comment-15095006 ] Poorna Chandra commented on PHOENIX-2478: - bq. Poorna Chandra - would be much appreciated if you

[jira] [Commented] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070292#comment-15070292 ] Poorna Chandra commented on PHOENIX-2525: - Can't you use a write pointer in such cases? > Views

[jira] [Commented] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070245#comment-15070245 ] Poorna Chandra commented on PHOENIX-2525: - [~jamestaylor] Read pointer is the largest committed

[jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067784#comment-15067784 ] Poorna Chandra commented on PHOENIX-2478: - [~jamestaylor] Here is the Tephra JIRA for this -

[jira] [Commented] (PHOENIX-2532) WAL is disabled for transactional tables

[ https://issues.apache.org/jira/browse/PHOENIX-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059836#comment-15059836 ] Poorna Chandra commented on PHOENIX-2532: - Thanks for reporting