[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

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

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210494#comment-16210494 ] James Taylor commented on PHOENIX-4292: --- +1. Nice work, [~tdsilva]. > Filters on Tables and Views

[jira] [Commented] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

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

[jira] [Updated] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4292: Attachment: PHOENIX-4292.patch [~jamestaylor] I thinks its a different issue. The test

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210440#comment-16210440 ] James Taylor commented on PHOENIX-4292: --- Do you think this is a duplicate of PHOENIX-3383? I have

[jira] [Updated] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4292: Summary: Filters on Tables and Views with composite PK of VARCHAR fields with sort

[jira] [Updated] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4292: Fix Version/s: 4.13.0 > Filters on Tables and Views with composite PK of VARCHAR fields

[jira] [Updated] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

[ https://issues.apache.org/jira/browse/PHOENIX-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4280: -- Attachment: PHOENIX-4280_v6.patch > Delete doesn't work when immutable indexes are in

[jira] [Updated] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

[ https://issues.apache.org/jira/browse/PHOENIX-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4280: -- Attachment: PHOENIX-4280_v5.patch > Delete doesn't work when immutable indexes are in

[jira] [Commented] (PHOENIX-4242) Fix Indexer post-compact hook logging of NPE and TableNotFound

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

[jira] [Commented] (PHOENIX-4298) refactoring to avoid using deprecated API for Put/Delete

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

[jira] [Commented] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

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

[jira] [Updated] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

[ https://issues.apache.org/jira/browse/PHOENIX-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4280: -- Attachment: PHOENIX-4280_v4.patch Attaching new version for test run. Will still clean up a

[jira] [Commented] (PHOENIX-4300) Do not use preIncrementAfterRowLock for UPSERT VALUES ON DUPLICATE KEY statement

[ https://issues.apache.org/jira/browse/PHOENIX-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210259#comment-16210259 ] James Taylor commented on PHOENIX-4300: --- No, no dependencies on HBase 2.0 features. > Do not use

[jira] [Commented] (PHOENIX-4300) Do not use preIncrementAfterRowLock for UPSERT VALUES ON DUPLICATE KEY statement

[ https://issues.apache.org/jira/browse/PHOENIX-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210234#comment-16210234 ] Geoffrey Jacoby commented on PHOENIX-4300: -- [~jamestaylor] - would this depend on any new HBase

[jira] [Updated] (PHOENIX-4100) Simplify mutable secondary index implementation

[ https://issues.apache.org/jira/browse/PHOENIX-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4100: -- Description: There's a lot of code for mutable secondary indexes, a lot of which is

[jira] [Updated] (PHOENIX-4100) Simplify mutable secondary index implementation

[ https://issues.apache.org/jira/browse/PHOENIX-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4100: -- Labels: HBase-2.0 (was: ) > Simplify mutable secondary index implementation >

Re: [DISCUSS] Road to HBase 2.0.0

FYI, I filed JIRAs for the Phoenix changes we talked about in the spreadsheet and labeled them all with HBase-2.0 [1]. [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%3D%22HBase-2.0%22 On Wed, Oct 18, 2017 at 3:38 PM,

[jira] [Updated] (PHOENIX-4297) Remove deprecated API umbrella

[ https://issues.apache.org/jira/browse/PHOENIX-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4297: -- Labels: HBase-2.0 (was: ) > Remove deprecated API umbrella > --

[jira] [Updated] (PHOENIX-4298) refactoring to avoid using deprecated API for Put/Delete

[ https://issues.apache.org/jira/browse/PHOENIX-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4298: -- Labels: HBase-2.0 (was: ) > refactoring to avoid using deprecated API for Put/Delete >

[jira] [Created] (PHOENIX-4301) Use operation.setPriority() instead of having our own PhoenixRpcSchedulerFactory

James Taylor created PHOENIX-4301: - Summary: Use operation.setPriority() instead of having our own PhoenixRpcSchedulerFactory Key: PHOENIX-4301 URL: https://issues.apache.org/jira/browse/PHOENIX-4301

Re: [DISCUSS] Road to HBase 2.0.0

On Wed, Oct 18, 2017 at 12:13 PM, Josh Elser wrote: > > On 10/18/17 2:51 PM, Andrew Purtell wrote: > >> Hopefully, Phoenix will not find itself in a position where >>> >> business-critical things it's doing are being removed from API (and >> Phoenix >> has no recourse to hack

[jira] [Updated] (PHOENIX-4300) Do not use preIncrementAfterRowLock for UPSERT VALUES ON DUPLICATE KEY statement

[ https://issues.apache.org/jira/browse/PHOENIX-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4300: -- Description: Instead of using Increment on the client and preIncrementAfterRowLock on the

[jira] [Updated] (PHOENIX-4300) Do not use preIncrementAfterRowLock for UPSERT VALUES ON DUPLICATE KEY statement

[ https://issues.apache.org/jira/browse/PHOENIX-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4300: -- Description: Instead of using Increment on the client and > Do not use

[jira] [Created] (PHOENIX-4300) Do not use preIncrementAfterRowLock for UPSERT VALUES ON DUPLICATE KEY statement

James Taylor created PHOENIX-4300: - Summary: Do not use preIncrementAfterRowLock for UPSERT VALUES ON DUPLICATE KEY statement Key: PHOENIX-4300 URL: https://issues.apache.org/jira/browse/PHOENIX-4300

[jira] [Updated] (PHOENIX-4242) Fix Indexer post-compact hook logging of NPE and TableNotFound

[ https://issues.apache.org/jira/browse/PHOENIX-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4242: -- Attachment: PHOENIX-4242.v4.master.patch [~giacomotaylor] version that just handles NPE and

[jira] [Updated] (PHOENIX-4298) refactoring to avoid using deprecated API for Put/Delete

[ https://issues.apache.org/jira/browse/PHOENIX-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-4298: - Attachment: PHOENIX-4298.patch Changes: Put.add => Put.addColumn Delete.deleteColumn =>

[jira] [Created] (PHOENIX-4299) Local index - Data vs index row count does not match

Mujtaba Chohan created PHOENIX-4299: --- Summary: Local index - Data vs index row count does not match Key: PHOENIX-4299 URL: https://issues.apache.org/jira/browse/PHOENIX-4299 Project: Phoenix

[jira] [Created] (PHOENIX-4298) refactoring to avoid using deprecated API for Put/Delete

Sergey Soldatov created PHOENIX-4298: Summary: refactoring to avoid using deprecated API for Put/Delete Key: PHOENIX-4298 URL: https://issues.apache.org/jira/browse/PHOENIX-4298 Project: Phoenix

[jira] [Updated] (PHOENIX-4297) Remove deprecated API umbrella

[ https://issues.apache.org/jira/browse/PHOENIX-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-4297: - Issue Type: Improvement (was: Bug) > Remove deprecated API umbrella >

[jira] [Created] (PHOENIX-4297) Remove deprecated API umbrella

Sergey Soldatov created PHOENIX-4297: Summary: Remove deprecated API umbrella Key: PHOENIX-4297 URL: https://issues.apache.org/jira/browse/PHOENIX-4297 Project: Phoenix Issue Type: Bug

Re: Date issue when copying data from Phoenix to Spark

Just a guess. Date is storying as the regular timestamp in GMT. So Phoenix shows you the GMT time while Spark is convert GMT time to you local time zone. Thanks, Sergey On Tue, Oct 17, 2017 at 3:54 PM, Pavani Addanki wrote: > I am trying to insert phoenix data into

[jira] [Commented] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

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

[jira] [Commented] (PHOENIX-4287) Incorrect aggregate query results when stats are disable for parallelization

[ https://issues.apache.org/jira/browse/PHOENIX-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209858#comment-16209858 ] Samarth Jain commented on PHOENIX-4287: --- Looks like it is limited to local indexes. Will keep

Re: [DISCUSS] Road to HBase 2.0.0

On 10/18/17 2:51 PM, Andrew Purtell wrote: Hopefully, Phoenix will not find itself in a position where business-critical things it's doing are being removed from API (and Phoenix has no recourse to hack what it needs back in place). I feel fairly confident this is going to happen given the

[jira] [Commented] (PHOENIX-4294) Allow scalar function to declare that it's not thread safe

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

[jira] [Commented] (PHOENIX-4295) Fix argument order for StatsCollectorIT derived classes

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

Re: [DISCUSS] Road to HBase 2.0.0

> Hopefully, Phoenix will not find itself in a position where business-critical things it's doing are being removed from API (and Phoenix has no recourse to hack what it needs back in place). I feel fairly confident this is going to happen given the radical excision of methods from the

Re: [DISCUSS] Road to HBase 2.0.0

Yes, the earlier the better, but this is also a bit chicken-and-egg. It's tough down in Phoenix to make sure it still works if the API we're trying to write against is still changing. I know that Anoop from the HBase side has been peering into the Phoenix side -- I've been operating under the

[jira] [Updated] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

[ https://issues.apache.org/jira/browse/PHOENIX-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4280: -- Attachment: PHOENIX-4280_v3.patch Still need to clean this up a bit, but there are a number

[jira] [Commented] (PHOENIX-4292) SOQL Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209696#comment-16209696 ] Thomas D'Silva commented on PHOENIX-4292: - Sure. > SOQL Filters on Tables and Views with

[jira] [Commented] (PHOENIX-4237) Allow sorting on (Java) collation keys for non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209676#comment-16209676 ] ASF GitHub Bot commented on PHOENIX-4237: - Github user JamesRTaylor commented on the issue:

[GitHub] phoenix issue #275: PHOENIX-4237: Add function to calculate Java collation k...

Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/275 Looking very good. Couple minor nits and the testing needs to be rounded out just a bit. ---

[jira] [Commented] (PHOENIX-4237) Allow sorting on (Java) collation keys for non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209673#comment-16209673 ] ASF GitHub Bot commented on PHOENIX-4237: - Github user JamesRTaylor commented on a diff in the

[GitHub] phoenix pull request #275: PHOENIX-4237: Add function to calculate Java coll...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/275#discussion_r145475530 --- Diff: phoenix-core/src/test/java/org/apache/phoenix/expression/function/CollationKeyFunctionTest.java --- @@ -0,0 +1,143 @@ +/* + *

[GitHub] phoenix pull request #275: PHOENIX-4237: Add function to calculate Java coll...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/275#discussion_r145475423 --- Diff: phoenix-core/src/test/java/org/apache/phoenix/expression/function/CollationKeyFunctionTest.java --- @@ -0,0 +1,143 @@ +/* + *

[jira] [Commented] (PHOENIX-4237) Allow sorting on (Java) collation keys for non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209670#comment-16209670 ] ASF GitHub Bot commented on PHOENIX-4237: - Github user JamesRTaylor commented on a diff in the

[GitHub] phoenix pull request #275: PHOENIX-4237: Add function to calculate Java coll...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/275#discussion_r145474350 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/expression/function/CollationKeyFunction.java --- @@ -0,0 +1,230 @@ +/* + * Licensed

[GitHub] phoenix pull request #275: PHOENIX-4237: Add function to calculate Java coll...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/275#discussion_r145473757 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/expression/function/CollationKeyFunction.java --- @@ -0,0 +1,230 @@ +/* + * Licensed

[jira] [Commented] (PHOENIX-4237) Allow sorting on (Java) collation keys for non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209669#comment-16209669 ] ASF GitHub Bot commented on PHOENIX-4237: - Github user JamesRTaylor commented on a diff in the

[jira] [Commented] (PHOENIX-4237) Allow sorting on (Java) collation keys for non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209667#comment-16209667 ] ASF GitHub Bot commented on PHOENIX-4237: - Github user JamesRTaylor commented on a diff in the

[GitHub] phoenix pull request #275: PHOENIX-4237: Add function to calculate Java coll...

Github user JamesRTaylor commented on a diff in the pull request: https://github.com/apache/phoenix/pull/275#discussion_r145473581 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/expression/function/CollationKeyFunction.java --- @@ -0,0 +1,230 @@ +/* + * Licensed

[jira] [Resolved] (PHOENIX-4294) Allow scalar function to declare that it's not thread safe

[ https://issues.apache.org/jira/browse/PHOENIX-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4294. --- Resolution: Fixed Fix Version/s: 4.13.0 > Allow scalar function to declare that it's

[jira] [Resolved] (PHOENIX-4295) Fix argument order for StatsCollectorIT derived classes

[ https://issues.apache.org/jira/browse/PHOENIX-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4295. --- Resolution: Fixed Fix Version/s: 4.13.0 > Fix argument order for StatsCollectorIT

[jira] [Assigned] (PHOENIX-4167) Phoenix SELECT query returns duplicate data in the same varchar/char column if a trim() is applied on the column AND a distinct arbitrary column is generated in the qu

[ https://issues.apache.org/jira/browse/PHOENIX-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumindu Buddhika reassigned PHOENIX-4167: - Assignee: Dumindu Buddhika > Phoenix SELECT query returns duplicate data in

[jira] [Commented] (PHOENIX-4296) Dead loop in HBase reverse scan when amount of scan data is greater than SCAN_RESULT_CHUNK_SIZE

[ https://issues.apache.org/jira/browse/PHOENIX-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209010#comment-16209010 ] Chen Feng commented on PHOENIX-4296: For example, if there are 3001 rows, whose ids are [1, 2, 3,

[jira] [Created] (PHOENIX-4296) Dead loop in HBase reverse scan when amount of scan data is greater than SCAN_RESULT_CHUNK_SIZE

rukawakang created PHOENIX-4296: --- Summary: Dead loop in HBase reverse scan when amount of scan data is greater than SCAN_RESULT_CHUNK_SIZE Key: PHOENIX-4296 URL: https://issues.apache.org/jira/browse/PHOENIX-4296

[jira] [Commented] (PHOENIX-4280) Delete doesn't work when immutable indexes are in building state

[ https://issues.apache.org/jira/browse/PHOENIX-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208915#comment-16208915 ] James Taylor commented on PHOENIX-4280: --- You're right, [~tdsilva]. Let me look at this closer. We