Re: [ANNOUNCE] New Phoenix committer: Ethan Wang

Congrats Ethan! Code reviews coming your way! ;) On Thu, Oct 12, 2017 at 10:38 AM, Mujtaba Chohan wrote: > Congrats Ethan!! > > On Thu, Oct 12, 2017 at 10:03 AM, Josh Elser wrote: > > > Congrats Ethan! > > > > > > On 10/11/17 9:45 PM, James Taylor wrote:

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC3

+1 Sanity testing on local install was fine. On Thu, Jun 7, 2018 at 11:37 AM, rajeshb...@apache.org < chrajeshbab...@gmail.com> wrote: > +1 > > Downloaded the source and ran all the tests they are fine. > > Thanks, > Rajeshbabu. > > On Thu, Jun 7, 2018 at 9:25 PM, Thomas D'Silva > wrote: > > >

Re: [DISCUSS] stop minor releases for 0.98 and 1.1

big +1 Commits have been way too burdensome On Tue, Jun 12, 2018 at 9:08 AM, Josh Elser wrote: > Also +1 > > Do that after the release? Or before? > > > On 6/12/18 11:55 AM, James Taylor wrote: > >> Somewhat orthogonal, but we should move master to a new 4.x-HBase-1.4 >> branch and make 5.x the

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC1

+1 Ran a test driver against a local instance which does concurrent batch upserts to an indexed table. Everything looked fine. On Tue, May 29, 2018 at 2:55 PM, Thomas D'Silva wrote: > +1 > > Successfully built from source and was able run all UTs/ITs. > > On Sun, May 27, 2018 at 2:55 PM, James

Re: [ANNOUNCE] New Phoenix committer: Karan Mehta

Congrats Karan, welcome! On Wed, Dec 27, 2017 at 7:52 AM, James Taylor wrote: > Congrats and welcome, Karan! > > On Tue, Dec 26, 2017 at 11:13 PM Thomas D'Silva > wrote: > > > On behalf of the Apache Phoenix PMC, I am pleased to announce that Karan >

Re: [ANNOUNCE] New Phoenix committer: Pedro Boado

Congrats Pedro! On Wed, Jan 31, 2018 at 6:25 AM, Ankit Singhal wrote: > Congrats and welcome, Pedro! > > On Wed, Jan 31, 2018 at 4:35 AM, Flavio Pompermaier > wrote: > > > Congratulations and thans for the great work! > > > > On 30 Jan 2018

Re: [VOTE] stop minor releases for 0.98 and 1.1

:03 PM, James Taylor wrote: > > > > +1 > > > > > > > > On Mon, Jul 9, 2018 at 3:55 PM, Vincent Poon < > > vincent.poon...@gmail.com> > > > > wrote: > > > > > > > >> This is a call to vote on stopping maintenanc

Re: [VOTE] stop minor releases for 0.98 and 1.1

The vote is now closed and passes with 5 binding +1s and no 0 or -1 votes. Phoenix 4.x-HBase-0.98 and 4.x-HBase-1.1 are now EOL and will no longer be maintained going forward. On Mon, Jul 16, 2018 at 11:18 AM, Vincent Poon wrote: > +1 > > On Wed, Jul 11, 2018 at 4:59 PM, Thoma

[ANNOUNCE] No more releases for Phoenix 0.98 and 1.1 branches

This is an announcement that 4.x-HBase-0.98 and 4.x-HBase-1.1 will no longer be maintained, as per the vote[1]. Thanks, The Apache Phoenix Team [1] http://mail-archives.apache.org/mod_mbox/phoenix-dev/201807.mbox/%3CCAHBoBrUALp0f3aSA%2BrFJ7c6mjEhgooVZyqpkRdvO9mRXE70jbw%40mail.gmail.com%3E

Re: [DISCUSS] stop minor releases for 0.98 and 1.1

Silva > wrote: > > > +1 on reducing the number of branches. > > > > On Tue, Jun 12, 2018 at 2:03 PM, Vincent Poon > > > wrote: > > > > > big +1 > > > Commits have been way too burdensome > > > > > > On Tue, Jun 12,

[VOTE] stop minor releases for 0.98 and 1.1

This is a call to vote on stopping maintenance of both the 4.x-HBase-0.98 and 4.x-HBase-1.1 branches. HBase 0.98 and 1.1 have been EOLed. To commit currently, it's usually 7 or more branches, which is a burden on devs. Vote will be open for at least 72 hours. Please vote: [ ] +1 approve [ ] +0

[VOTE] Release of Apache Phoenix 4.14.1 RC0

Hello Everyone, This is a call for a vote on Apache Phoenix 4.14.1 RC0. This is a patch release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1, 1.2, 1.3, 1.4. The release includes both a source-only release and a convenience binary release for each supported HBase version. This

Re: Regarding the Secondary Index write path

If the table has no indexes, the Indexer coprocessor won't be loaded. As for your original question, the answer is a little nuanced. For Phoenix 4.14+: The index updates are calculated in preBatchMutate, and the index updates are written in postBatchMutate. So from HRegion#doMiniBatchMutation,

Re: Regarding the Secondary Index write path

t; > Correct me if I am wrong in assuming that WALEdit in preBatchMutate is > different from the wal edits that will be generated for data table. > Once again thanks for the quick response. > > > On Tue, Oct 30, 2018 at 4:16 PM Vincent Poon > wrote: > >> If the table ha

Re: [VOTE] Release of Apache Phoenix 4.14.1 RC0

is cleaned up in the future: > > > ./bin/phoenix_utils.pyc > > > > > > Everything else looks good to me. > > > > > > - Josh > > > > > > On Tue, Oct 30, 2018 at 4:47 PM Vincent Poon < > vincent.poon...@gmail.com> > > &g

Re: [VOTE] Release of Apache Phoenix 4.14.1 RC0

The vote is now closed and passes with 4 binding +1s and no 0 or -1 votes. Thanks to those who voted. We'll work on pushing out the bits next. On Thu, Nov 8, 2018 at 3:52 PM Vincent Poon wrote: > +1 > Ran mvn verify on all branches. A few errors passed after manually > running.

[ANNOUNCE] Apache Phoenix 4.14.1 released

The Apache Phoenix team is pleased to announce the immediate availability of the 4.14.1 patch release. Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop using Apache HBase as its backing store and providing integration with other projects in the Apache ecosystem

Re: [DISCUSS] Next 5.x release?

r and call it 5.1.0 instead. > > On 9/27/18 12:16 AM, Vincent Poon wrote: > > You're right, Josh, I was mistaken, there was indeed a 5.0.0 release. > But > > I meant the same as your last bit - branch off 5.0.0 and only put in > HBase > > 2.0.2 and critical fixes for 5.0.1.

Re: [DISCUSS] Next 5.x release?

The 5.0.0 release apparently was an 'alpha'. I think we should do a 5.0.1 which can work with HBase 2.0.2 and remove the 'alpha'. 5.0 has feature parity with 4.14. 5.1 would have feature parity with 4.15, the main addition being splittable syscat On a sidenote, I've been planning a 4.14.1

Re: [DISCUSS] Next 5.x release?

5.x (from the master branch). > > In a similar vein, we could also branch off of the 5.0.0 release and > cherry-pick back critical changes to make a proper 5.0.1 if a 5.1.0 is > still a ways off (as above) > > On 9/26/18 6:18 PM, Vincent Poon wrote: > > The 5.0.0 release app

Re: [ANNOUNCE] New Phoenix PMC member: Karan Mehta

Congrats Karan! On Wed, Dec 12, 2018 at 9:17 AM Andrew Purtell wrote: > Congratulations and welcome, Karan. > > On Tue, Dec 11, 2018 at 8:38 PM Thomas D'Silva wrote: > > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Karan > > Mehta has accepted our invitation to join the

Re: [ANNOUNCE] New Phoenix committer: Chinmay Kulkarni

Congrats, Chinmay! On Mon, Dec 10, 2018 at 10:57 PM Karan Mehta wrote: > Congrats Chinmay! > ᐧ > > On Mon, Dec 10, 2018 at 10:10 PM Geoffrey Jacoby > wrote: > > > Congratulations, Chinmay! > > > > Geoffrey Jacoby > > > > On Mon, Dec 10, 2018 at 1:45 PM Thomas D'Silva > wrote: > > > > > On

Re: [ANNOUNCE] New Phoenix committer: Jaanai Zhang

Congrats, Jaanai ! On Mon, Dec 10, 2018 at 10:13 PM Geoffrey Jacoby wrote: > Congratulations, Jaanai! > > On Mon, Dec 10, 2018 at 2:05 PM Thomas D'Silva wrote: > > > On behalf of the Apache Phoenix PMC, I am pleased to announce that Jaanai > > Zhang has accepted our invitation to become a

Re: [DISCUSS] Drop support for java 1.7 on the 1.2, 1.3 and 1.4 branches

+1 to another repo for connectors On Mon, Dec 3, 2018 at 6:27 PM James Taylor wrote: > +1. Good idea, Thomas. > > On Mon, Dec 3, 2018 at 2:57 PM Thomas D'Silva > wrote: > > > I believe we will be maintaining the 4.x branches which support HBase > 1.2, > > 1.3 and 1.4 for a while. > > Should we

Re: [DISCUSS] phoenix-connectors and phoenix-queryserver release process

Right now the "presto connector" I'm working on also builds an uber jar that is like phoenix-client but with some additional excludes and relocations. So I would need to build one for each Phoenix release. So I was thinking of something like: phoenix-client-4.14.1-HBase-1.4-presto-1.0.0.jar I

Re: [ANNOUNCE] New Phoenix committer: Abhishek Singh Chouhan

Congratulations Abhishek! On Fri, Apr 5, 2019 at 10:46 AM Thomas D'Silva wrote: > On behalf of the Apache Phoenix PMC, I am pleased to announce that > Abhishek Singh > Chouhan has accepted our invitation to become a committer. Abhishek has > fixed several bugs[1] (including an important one

Re: [DRAFT] board report feb 2019

+1 On Tue, Feb 5, 2019 at 11:03 AM Thomas D'Silva wrote: > LGTM > > On Tue, Feb 5, 2019 at 8:41 AM Josh Elser wrote: > > > All, > > > > Please take the time to review what I have below and propose any > > additions/modifications you think appropriate. Unless I hear requests > > otherwise, I'll

Re: Build failure

Sorry, will revert for now On Mon, Jan 28, 2019 at 3:10 PM Gerald Sangudi wrote: > Hi folks, > > The build is failing for me on the latest master. I also tried a fresh > install. > > The latest commit that's failing is > >

Re: [ANNOUNCE] New Phoenix PMC member: Geoffrey Jacoby

Congrats Geoffrey! On Tue, Apr 9, 2019 at 11:42 AM Thomas D'Silva wrote: > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Geoffrey > Jacoby has accepted our invitation to join the PMC. > > Please join me in congratulating Geoffrey. > > Thanks, > Thomas >

Re: [ANNOUNCE] New Phoenix PMC member: Cheng Lei

Congrats Cheng! On Tue, Apr 9, 2019 at 11:42 AM Thomas D'Silva wrote: > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Cheng > Lei has accepted our invitation to join the PMC. > > Please join me in congratulating Cheng. > > Thanks, > Thomas >

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC2

21908ecb7cbf05089e6214682bce634e1f3274205cb13f1bfcb8683fe > > *apache-phoenix-4.14.2-HBase-1.4-src.tar.gz > > --- > > > apache-phoenix-4.14.2-HBase-1.4-src.tar.gz: > > > EB8CF855 3A53A073 2E4717F5 D523A23F 9432A6F5 EB3769DC 330C4E75 999460CE > > 36CBE6E2 >

Re: [ANNOUNCE] New committer Swaroopa Kadam

Congrats Swaroopa, looking forward to more patches On Tue, May 28, 2019 at 4:33 PM Xu Cang wrote: > Congrats! :) > > On Tue, May 28, 2019 at 4:18 PM Priyank Porwal > wrote: > > > Congrats Swaroopa! > > > > On Tue, May 28, 2019, 3:24 PM Andrew Purtell > wrote: > > > > > Congratulations

Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

I think the confusion here is stemming from two different things: 1) Moving docs from SVN to git (potentially its own repo) 2) Moving docs into the same apache/phoenix repo as the source code. I think we should do #1, and not #2, which avoids the concerns Thomas and James have. On Mon, Jun 3,

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC2

+1 deployed locally on pseudo-distributed cluster, ran some basic sanity tests On Fri, May 24, 2019 at 11:50 AM Andrew Purtell wrote: > Let me raise this on dev@hbase > > On Fri, May 24, 2019 at 11:45 AM Thomas D'Silva > wrote: > > > We can't commit PHOENIX-5269 to 4.14-HBase-1.3 until HBase

Re: [DISCUSS] Drop support for HBase-1.2

+1 On Sun, May 12, 2019 at 8:18 PM Andrew Purtell wrote: > +1 > > I would think it would be a drain on committer time to keep having to > accommodate interface differences on the EOL line. > > > On May 10, 2019, at 1:28 PM, Thomas D'Silva > wrote: > > > > Since HBase 1.2 is now end of life and

Re: [DISCUSS] Board report due 2019/08/14

4.14.2 released, 4.14.3 nearing completion PHOENIX-5156 for consistent global indexes is a big improvement New integrations with Presto and Spark On Tue, Aug 13, 2019 at 9:36 AM William Shen wrote: > A couple things that might be noteworthy: > - Thanks to Lars, we now have a fully passing

Re: [VOTE] Release of Apache Phoenix 4.14.3 RC1

I saw the the same flapping with SaltedIndexIT On Mon, Aug 12, 2019 at 4:48 PM Geoffrey Jacoby wrote: > Vote: -1, for the same reason as Artem above. > > (I also agree with Artem that the Maven problems he identified aren't > blockers for this release, though we need to fix them for the future.

Re: [VOTE] Release of Apache Phoenix 4.14.3 RC2

+1 Ran the core tests which passed, except for SaltedIndexIT (it seems that is failing consistently for people when run as part of full suite?). In any case, not a blocker. On Fri, Aug 16, 2019 at 1:39 PM Geoffrey Jacoby wrote: > Vote: +1 > > rat-check: OK > Signature-check: OK > Checksums: OK

Re: Phoenix Connector on Secure Cluster

Try using an hbase-site.xml (on both HBase server and presto-phoenix client) with the following properties: hbase.security.authentication (set to ‘kerberos’), hadoop.security.authentication (set to ‘kerberos’), hbase.regionserver.kerberos.principal, hbase.regionserver.keytab.file,

Re: [ANNOUNCE] New Phoenix PMC Member: Chinmay Kulkarni

Congrats, Chinmay! On Mon, Aug 26, 2019 at 10:34 AM Geoffrey Jacoby wrote: > Each Apache project is governed by a Project Management Committee, or PMC. > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Chinmay > Kulkarni has accepted our invitation to join. Chinmay has been a

Re: question about Presto on Phoenix.

Not sure if you're the same person, but there is an issue open https://github.com/prestosql/presto/issues/1271 Unfortunately, I've been pretty busy lately and haven't had time to try any newer versions. If you want to try yourself, you could start by building the phoenix-client 'embedded'

Re: [VOTE] Accept Tephra and Omid podlings as Phoenix sub-projects

+1 On Wed, Oct 30, 2019 at 8:57 AM William Shen wrote: > +1! > > On Wed, Oct 30, 2019 at 8:27 AM Josh Elser wrote: > > > Hi, > > > > As was previously discussed[1][2], there is a motion to "adopt" the > > Tephra and Omid podlings as sub-projects to Apache Phoenix. A > > sub-project is a

Re: [VOTE] Release of Apache Phoenix 4.15.0 RC1

+1 (Binding) Did some sanity testing with old client and new server. Creating tables, global/local indexes, etc. all seemed fine. On Thu, Nov 21, 2019 at 12:58 PM la...@apache.org wrote: > I agree that PHOENIX-5529 and PHOENIX-5580 are longstanding issues and > not blockers for 4.15.0. My

Re: [VOTE] Release of Apache Phoenix 4.15.0 RC0

d. :( > -- Lars > On Friday, October 18, 2019, 04:09:11 PM PDT, Vincent Poon < > vincentp...@apache.org> wrote: > > I'm also not able to create an index with the older client: > > 2019-10-18 16:06:26,569 ERROR > [RpcServer.FifoWFPBQ.default.handler=255,queue=21,p

Re: [VOTE] Release of Apache Phoenix 4.15.0 RC0

-1 I still see PHOENIX-5103 still cropping up for "DROP TABLE" when using the 4.14 client against 4.15 server. However, it seems "CREATE TABLE" works fine. Caused by: org.apache.hadoop.hbase.TableNotFoundException: org.apache.hadoop.hbase.TableNotFoundException: Table 'SYSTEM:CHILD_LINK' was not

Re: [VOTE] Release of Apache Phoenix 4.15.0 RC0

:2373) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:188) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:168) On Fri, Oct 18, 2019 at 3:21 PM Vincent Poon wrote: > -1 > I sti

Re: [DISCUSS] Omid and Tephra podlings

+1 I don't think pulling these under Phoenix would change their volume of activity in the near term. However, when/if usage of transactions with Phoenix increases, we'd want a path forward to be able to make modifications where necessary to these projects. This seems the best way to ensure there's

[jira] [Created] (PHOENIX-2787) support IF EXISTS for ALTER TABLE SET options

Vincent Poon created PHOENIX-2787: - Summary: support IF EXISTS for ALTER TABLE SET options Key: PHOENIX-2787 URL: https://issues.apache.org/jira/browse/PHOENIX-2787 Project: Phoenix Issue

[jira] [Created] (PHOENIX-3334) ConnectionQueryServicesImpl should close HConnection if init fails

Vincent Poon created PHOENIX-3334: - Summary: ConnectionQueryServicesImpl should close HConnection if init fails Key: PHOENIX-3334 URL: https://issues.apache.org/jira/browse/PHOENIX-3334 Project

[jira] [Commented] (PHOENIX-3806) IndexUpdateManager spending a lot of time sorting mutations on Index rebuild

[ https://issues.apache.org/jira/browse/PHOENIX-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982230#comment-15982230 ] Vincent Poon commented on PHOENIX-3806: --- What I find is that if I create 100 versions of a row

[jira] [Commented] (PHOENIX-4057) Do not issue index updates for out of order mutation during index maintenance

[ https://issues.apache.org/jira/browse/PHOENIX-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111757#comment-16111757 ] Vincent Poon commented on PHOENIX-4057: --- [~jamestaylor] I guess this would also mean we can't run

[jira] [Commented] (PHOENIX-3994) Index RPC priority still depends on the controller factory property in hbase-site.xml

[ https://issues.apache.org/jira/browse/PHOENIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086062#comment-16086062 ] Vincent Poon commented on PHOENIX-3994: --- v4 patch lgtm, [~samarthjain] > Index RPC priority st

[jira] [Updated] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3948: -- Attachment: PHOENIX-3948.master.v2.patch > Enable shorter time outs for server-side in

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086550#comment-16086550 ] Vincent Poon commented on PHOENIX-3807: --- Apologies [~elserj], forgot about that and forgot

[jira] [Commented] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081268#comment-16081268 ] Vincent Poon commented on PHOENIX-3948: --- [~gjacoby] Yea an operator would need to add this new

[jira] [Updated] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3948: -- Attachment: PHOENIX-3948.master.v1.patch > Enable shorter time outs for server-side in

[jira] [Assigned] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon reassigned PHOENIX-3948: - Assignee: Vincent Poon > Enable shorter time outs for server-side index wri

[jira] [Commented] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081215#comment-16081215 ] Vincent Poon commented on PHOENIX-3948: --- [~jamestaylor] [~samarthjain] I was able to set

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084407#comment-16084407 ] Vincent Poon commented on PHOENIX-3807: --- [~elserj] 100% agree with your naming suggestions. I

[jira] [Updated] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3948: -- Attachment: PHOENIX-3948.master.v3.patch New v3 patch sets the timeout at 48 seconds, less

[jira] [Commented] (PHOENIX-4051) Prevent out-of-order updates for mutable index updates

[ https://issues.apache.org/jira/browse/PHOENIX-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104172#comment-16104172 ] Vincent Poon commented on PHOENIX-4051: --- Hey [~jamestaylor] , I see this in HRegion: {code

[jira] [Created] (PHOENIX-4050) Index rows created by 4.9 client against 4.10 server are not deleted properly

Vincent Poon created PHOENIX-4050: - Summary: Index rows created by 4.9 client against 4.10 server are not deleted properly Key: PHOENIX-4050 URL: https://issues.apache.org/jira/browse/PHOENIX-4050

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093576#comment-16093576 ] Vincent Poon commented on PHOENIX-3807: --- +1 [~elserj] > Add server level metrics for second

[jira] [Commented] (PHOENIX-4042) Add hadoop-metrics2 server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093879#comment-16093879 ] Vincent Poon commented on PHOENIX-4042: --- +1, thanks [~elserj] ! > Add hadoop-metrics2 ser

[jira] [Commented] (PHOENIX-3994) Index RPC priority still depends on the controller factory property in hbase-site.xml

[ https://issues.apache.org/jira/browse/PHOENIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084815#comment-16084815 ] Vincent Poon commented on PHOENIX-3994: --- [~samarthjain] I looked at the comment you linked

[jira] [Commented] (PHOENIX-3994) Index RPC priority still depends on the controller factory property in hbase-site.xml

[ https://issues.apache.org/jira/browse/PHOENIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084641#comment-16084641 ] Vincent Poon commented on PHOENIX-3994: --- [~samarthjain] changes LGTM overall, but had one question

[jira] [Updated] (PHOENIX-4039) Increase default number of RPC retries for our index rebuild task

[ https://issues.apache.org/jira/browse/PHOENIX-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4039: -- Attachment: PHOENIX-4039_addendum.patch > Increase default number of RPC retries for

[jira] [Commented] (PHOENIX-4039) Increase default number of RPC retries for our index rebuild task

[ https://issues.apache.org/jira/browse/PHOENIX-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095429#comment-16095429 ] Vincent Poon commented on PHOENIX-4039: --- [~jamestaylor] Attached addendum > Increase defa

[jira] [Commented] (PHOENIX-3983) Index rebuild scans should not be using the ServerRpcControllerFactory

[ https://issues.apache.org/jira/browse/PHOENIX-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068747#comment-16068747 ] Vincent Poon commented on PHOENIX-3983: --- The patch fixes the data table scans by specifically

[jira] [Commented] (PHOENIX-3983) Index rebuild scans should not be using the ServerRpcControllerFactory

[ https://issues.apache.org/jira/browse/PHOENIX-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070701#comment-16070701 ] Vincent Poon commented on PHOENIX-3983: --- HBASE-15816 requires us to set the priority on each

[jira] [Commented] (PHOENIX-3983) Index rebuild scans should not be using the ServerRpcControllerFactory

[ https://issues.apache.org/jira/browse/PHOENIX-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071725#comment-16071725 ] Vincent Poon commented on PHOENIX-3983: --- [~lhofhansl] Yes, check out the controller setPriority

[jira] [Commented] (PHOENIX-3806) IndexUpdateManager spending a lot of time sorting mutations on Index rebuild

[ https://issues.apache.org/jira/browse/PHOENIX-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981677#comment-15981677 ] Vincent Poon commented on PHOENIX-3806: --- Some more detail on this issue: What we found

[jira] [Created] (PHOENIX-3810) index_disable_timestamp not set by ALTER INDEX DISABLE

Vincent Poon created PHOENIX-3810: - Summary: index_disable_timestamp not set by ALTER INDEX DISABLE Key: PHOENIX-3810 URL: https://issues.apache.org/jira/browse/PHOENIX-3810 Project: Phoenix

[jira] [Commented] (PHOENIX-2460) Implement scrutiny command to validate whether or not an index is in sync with the data table

[ https://issues.apache.org/jira/browse/PHOENIX-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131556#comment-16131556 ] Vincent Poon commented on PHOENIX-2460: --- [~jamestaylor] [~samarthjain] Mind taking a look

[jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994307#comment-15994307 ] Vincent Poon commented on PHOENIX-3824: --- [~lhofhansl] it turned out that the two are related

[jira] [Commented] (PHOENIX-3847) Handle out of order rows during index maintenance

[ https://issues.apache.org/jira/browse/PHOENIX-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008933#comment-16008933 ] Vincent Poon commented on PHOENIX-3847: --- [~jamestaylor] Tried this out and the behavior seems

[jira] [Commented] (PHOENIX-3847) Handle out of order rows during index maintenance

[ https://issues.apache.org/jira/browse/PHOENIX-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008938#comment-16008938 ] Vincent Poon commented on PHOENIX-3847: --- I guess then point queries wouldn't work. Hmm yea

[jira] [Updated] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3825: -- Attachment: PHOENIX-3825.master.v1.patch > Mutable Index rebuild does not write an in

[jira] [Assigned] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon reassigned PHOENIX-3825: - Assignee: Vincent Poon Affects Version/s: 4.11.0

[jira] [Commented] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003653#comment-16003653 ] Vincent Poon commented on PHOENIX-3825: --- [~jamestaylor] Any idea what this method

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014516#comment-16014516 ] Vincent Poon commented on PHOENIX-3807: --- [~elserj] Cool, I'm working on HBASE-18060 which

[jira] [Commented] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

[ https://issues.apache.org/jira/browse/PHOENIX-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003772#comment-16003772 ] Vincent Poon commented on PHOENIX-3825: --- Actually, looking at TestIndexUpdateManager, looks like

[jira] [Updated] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3807: -- Attachment: PHOENIX-3807.v1.master.patch > Add server level metrics for secondary inde

[jira] [Updated] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3807: -- Attachment: (was: PHOENIX-3807.v1.master.patch) > Add server level metrics for second

[jira] [Created] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

Vincent Poon created PHOENIX-3824: - Summary: Mutable Index partial rebuild adds more than one index row for updated data row Key: PHOENIX-3824 URL: https://issues.apache.org/jira/browse/PHOENIX-3824

[jira] [Created] (PHOENIX-3825) Mutable Index rebuild does not write an index version for each data row version

Vincent Poon created PHOENIX-3825: - Summary: Mutable Index rebuild does not write an index version for each data row version Key: PHOENIX-3825 URL: https://issues.apache.org/jira/browse/PHOENIX-3825

[jira] [Updated] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3824: -- Attachment: PHOENIX-3824.v1.patch > Mutable Index partial rebuild adds more than one in

[jira] [Updated] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3824: -- Attachment: PHOENIX-3824.v2.patch Fixed line lengths and test timeout > Mutable In

[jira] [Updated] (PHOENIX-3806) IndexUpdateManager spending a lot of time sorting mutations on Index rebuild

[ https://issues.apache.org/jira/browse/PHOENIX-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3806: -- Attachment: PHOENIX-3806.v1.patch > IndexUpdateManager spending a lot of time sort

[jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001541#comment-16001541 ] Vincent Poon commented on PHOENIX-3824: --- [~lhofhansl] Yes it's a hot code path in that it's called

[jira] [Commented] (PHOENIX-3824) Mutable Index partial rebuild adds more than one index row for updated data row

[ https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997685#comment-15997685 ] Vincent Poon commented on PHOENIX-3824: --- [~jamestaylor] Can you take a look at the logic

[jira] [Commented] (PHOENIX-3806) IndexUpdateManager spending a lot of time sorting mutations on Index rebuild

[ https://issues.apache.org/jira/browse/PHOENIX-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997680#comment-15997680 ] Vincent Poon commented on PHOENIX-3806: --- put up a patch that simply changes the SortedCollection

[jira] [Updated] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3807: -- Attachment: PHOENIX-3807.v1.master.patch Here's a patch which uses the HBase native metrics

[jira] [Updated] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-3807: -- Attachment: Screen Shot 2017-05-31 at 4.00.16 PM.png example pic of what the metrics look

[jira] [Comment Edited] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032161#comment-16032161 ] Vincent Poon edited comment on PHOENIX-3807 at 5/31/17 11:01 PM: - Here's

[jira] [Updated] (PHOENIX-4169) Explicitly cap timeout for index disable RPC on compaction

[ https://issues.apache.org/jira/browse/PHOENIX-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4169: -- Attachment: PHOENIX-4169.master.patch PHOENIX-4169.0.98.patch > Explici

[jira] [Commented] (PHOENIX-4214) Scans which write should not block region split or close

[ https://issues.apache.org/jira/browse/PHOENIX-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168806#comment-16168806 ] Vincent Poon commented on PHOENIX-4214: --- [~lhofhansl] Yes, this patch blocks only new write

[jira] [Updated] (PHOENIX-4219) Index gets out of sync on HBase 1.x

[ https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4219: -- Attachment: PHOENIX-4219_test.patch > Index gets out of sync on HBase

[jira] [Created] (PHOENIX-4219) Index gets out of sync on HBase 1.x

Vincent Poon created PHOENIX-4219: - Summary: Index gets out of sync on HBase 1.x Key: PHOENIX-4219 URL: https://issues.apache.org/jira/browse/PHOENIX-4219 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-4214) Scans which write should not block region split or close

[ https://issues.apache.org/jira/browse/PHOENIX-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4214: -- Attachment: PHOENIX-4214.master.v1.patch Attaching patch for master, [~jamestaylor

  1   2   3   4   5   6   >