[jira] [Commented] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129887#comment-16129887 ] Hadoop QA commented on PHOENIX-4089: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL

[ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129785#comment-16129785 ] Hadoop QA commented on PHOENIX-3817: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4089: -- Attachment: PHOENIX-4089_v4.patch Fixed test issue and removed unnecessary code. The code

[jira] [Created] (PHOENIX-4092) Ensure index and table remains in sync when the table is mutating

James Taylor created PHOENIX-4092: - Summary: Ensure index and table remains in sync when the table is mutating Key: PHOENIX-4092 URL: https://issues.apache.org/jira/browse/PHOENIX-4092 Project:

[jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL

[ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129753#comment-16129753 ] Andrew Purtell commented on PHOENIX-3817: - [~alexaraujo] Example usage in the help string

[jira] [Commented] (PHOENIX-4076) Move master branch up to HBase 1.4.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/PHOENIX-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129731#comment-16129731 ] Andrew Purtell commented on PHOENIX-4076: - FWIW I'm testing replication using [~vincentpoon]'s

[jira] [Commented] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129708#comment-16129708 ] Hadoop QA commented on PHOENIX-4089: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3817) VerifyReplication using SQL

[ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated PHOENIX-3817: Attachment: PHOENIX-3817.v4.patch Here's a v4 patch that fixes [ERROR]

[jira] [Commented] (PHOENIX-4080) The error message for version mismatch is not accurate.

[ https://issues.apache.org/jira/browse/PHOENIX-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129673#comment-16129673 ] Hadoop QA commented on PHOENIX-4080: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-4080) The error message for version mismatch is not accurate.

[ https://issues.apache.org/jira/browse/PHOENIX-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129661#comment-16129661 ] Geoffrey Jacoby commented on PHOENIX-4080: -- [~aertoria] - Definitely an improvement, and thanks

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129655#comment-16129655 ] James Taylor commented on PHOENIX-3163: --- Ping [~aertoria] - this is one of the split JIRAs I

[jira] [Updated] (PHOENIX-4080) The error message for version mismatch is not accurate.

[ https://issues.apache.org/jira/browse/PHOENIX-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang updated PHOENIX-4080: Attachment: PHOENIX-4080.patch > The error message for version mismatch is not accurate. >

[jira] [Assigned] (PHOENIX-4080) The error message for version mismatch is not accurate.

[ https://issues.apache.org/jira/browse/PHOENIX-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang reassigned PHOENIX-4080: --- Assignee: Ethan Wang > The error message for version mismatch is not accurate. >

[jira] [Updated] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4089: -- Attachment: PHOENIX_4089_v3.patch Fixing some test failures. Still need to call partial index

[jira] [Commented] (PHOENIX-4080) The error message for version mismatch is not accurate.

[ https://issues.apache.org/jira/browse/PHOENIX-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129580#comment-16129580 ] Ethan Wang commented on PHOENIX-4080: - That's the place. I put up a patch real quick then New one

[jira] [Commented] (PHOENIX-4088) SQLExceptionCode.java code beauty and typos

[ https://issues.apache.org/jira/browse/PHOENIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129562#comment-16129562 ] Josh Elser commented on PHOENIX-4088: - LGTM, pending QA. Thanks for the patch, Csaba! I've made you

[jira] [Assigned] (PHOENIX-4088) SQLExceptionCode.java code beauty and typos

[ https://issues.apache.org/jira/browse/PHOENIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser reassigned PHOENIX-4088: --- Assignee: Csaba Skrabak > SQLExceptionCode.java code beauty and typos >

[jira] [Commented] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129529#comment-16129529 ] Hadoop QA commented on PHOENIX-4089: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Created] (PHOENIX-4091) Document TABLESAMPLE feature

James Taylor created PHOENIX-4091: - Summary: Document TABLESAMPLE feature Key: PHOENIX-4091 URL: https://issues.apache.org/jira/browse/PHOENIX-4091 Project: Phoenix Issue Type: Task

[jira] [Commented] (PHOENIX-4047) Configuration Profile Feature

[ https://issues.apache.org/jira/browse/PHOENIX-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129522#comment-16129522 ] Sergey Soldatov commented on PHOENIX-4047: -- [~gjacoby] well, as you correctly mentioned there

[jira] [Commented] (PHOENIX-4047) Configuration Profile Feature

[ https://issues.apache.org/jira/browse/PHOENIX-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129504#comment-16129504 ] Geoffrey Jacoby commented on PHOENIX-4047: -- [~sergey.soldatov] - let's say you have two use

[jira] [Commented] (PHOENIX-4047) Configuration Profile Feature

[ https://issues.apache.org/jira/browse/PHOENIX-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129495#comment-16129495 ] Ethan Wang commented on PHOENIX-4047: - [~arijo] Sorry. I think I was meant to add Alex Araujo >

[jira] [Commented] (PHOENIX-4080) The error message for version mismatch is not accurate.

[ https://issues.apache.org/jira/browse/PHOENIX-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129493#comment-16129493 ] Ethan Wang commented on PHOENIX-4080: - I wonder this is the one. I will give it a try and confirm

[jira] [Commented] (PHOENIX-3965) Github repo read me need to update

[ https://issues.apache.org/jira/browse/PHOENIX-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129460#comment-16129460 ] Ethan Wang commented on PHOENIX-3965: - Sure![~elserj] > Github repo read me need to update >

Re: HTrace may be heading for the attic and support for same be removed from HBase

If we want to preserve the existing framework, htrace needs maintainers. Otherwise it's going to the attic and Hadoop and HBase will surely remove support for it. I do not know of any functional replacements for htrace. On Wed, Aug 16, 2017 at 12:30 PM, James Taylor

[jira] [Updated] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4089: -- Attachment: PHOENIX_4089_v2.patch Please review, [~tdsilva] > Prevent index from getting out

Re: HTrace may be heading for the attic and support for same be removed from HBase

What's the way of collecting metrics through the full stack (RS + HDFS) when the client performs an operation? Or is the conclusion that this isn't useful? Or maybe impossible? Does something else replace some/all of the htrace functionality (HBase metrics framework?) That'd be fine if folks were

Re: HTrace may be heading for the attic and support for same be removed from HBase

If someone involved with Phoenix dev would like to see htrace continue, I'd recommend volunteering on the thread at dev@htrace to keep the podling alive and out of the attic. On Wed, Aug 16, 2017 at 11:56 AM, Andrew Purtell wrote: > None. > > And it wouldn't really matter

Re: HTrace may be heading for the attic and support for same be removed from HBase

None. And it wouldn't really matter if htrace goes to the attic. It's dead / read only at that point. On Wed, Aug 16, 2017 at 11:52 AM, James Taylor wrote: > What's the proposed alternative? > > On Wed, Aug 16, 2017 at 11:03 AM, Andrew Purtell >

Re: HTrace may be heading for the attic and support for same be removed from HBase

What's the proposed alternative? On Wed, Aug 16, 2017 at 11:03 AM, Andrew Purtell wrote: > HTrace is lacking momentum and may be headed for the attic. > > See > https://lists.apache.org/thread.html/ff87eb11bbfc3ca27a83c0ab377459 >

HTrace may be heading for the attic and support for same be removed from HBase

HTrace is lacking momentum and may be headed for the attic. See https://lists.apache.org/thread.html/ff87eb11bbfc3ca27a83c0ab377459767a46175447f763b1bf052987@%3Cdev.htrace.apache.org%3E ​HBase is considering removal of all HTrace related code. See

[jira] [Created] (PHOENIX-4090) Remove HTrace based tracing

Andrew Purtell created PHOENIX-4090: --- Summary: Remove HTrace based tracing Key: PHOENIX-4090 URL: https://issues.apache.org/jira/browse/PHOENIX-4090 Project: Phoenix Issue Type: Task

[jira] [Commented] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129001#comment-16129001 ] Hadoop QA commented on PHOENIX-4089: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4089: -- Attachment: PHOENIX-4089_v1.patch > Prevent index from getting out of sync with data table

[jira] [Updated] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4089: -- Attachment: PHOENIX-4089_4.x-HBase-0.98_v2.patch > Prevent index from getting out of sync

[jira] [Assigned] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4089: - Assignee: James Taylor Fix Version/s: 4.12.0 > Prevent index from getting out

[jira] [Updated] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

[ https://issues.apache.org/jira/browse/PHOENIX-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4089: -- Attachment: PHOENIX-4089_4.x-HBase-0.98.patch > Prevent index from getting out of sync with

[jira] [Created] (PHOENIX-4089) Prevent index from getting out of sync with data table under high concurrency

James Taylor created PHOENIX-4089: - Summary: Prevent index from getting out of sync with data table under high concurrency Key: PHOENIX-4089 URL: https://issues.apache.org/jira/browse/PHOENIX-4089

[jira] [Updated] (PHOENIX-4088) SQLExceptionCode.java code beauty and typos

[ https://issues.apache.org/jira/browse/PHOENIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Csaba Skrabak updated PHOENIX-4088: --- Attachment: PHOENIX-4088.patch > SQLExceptionCode.java code beauty and typos >

[jira] [Created] (PHOENIX-4088) SQLExceptionCode.java code beauty and typos

Csaba Skrabak created PHOENIX-4088: -- Summary: SQLExceptionCode.java code beauty and typos Key: PHOENIX-4088 URL: https://issues.apache.org/jira/browse/PHOENIX-4088 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128772#comment-16128772 ] Hudson commented on PHOENIX-4083: - SUCCESS: Integrated in Jenkins build Phoenix-master #1732 (See

[jira] [Commented] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128604#comment-16128604 ] Hudson commented on PHOENIX-4083: - FAILURE: Integrated in Jenkins build Phoenix-master #1731 (See

[jira] [Assigned] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-4083: -- Assignee: JC > Incorrect conditional when including OFFSET into explain plan >

[jira] [Resolved] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-4083. Resolution: Fixed Fix Version/s: 4.12.0 > Incorrect conditional when including

[jira] [Comment Edited] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128594#comment-16128594 ] Ankit Singhal edited comment on PHOENIX-4083 at 8/16/17 10:14 AM: --

[jira] [Commented] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128594#comment-16128594 ] Ankit Singhal commented on PHOENIX-4083: yes.. my bad. Thanks [~lifove] for pointing out. Just