[jira] [Updated] (PHOENIX-5109) Hinted local index with uncovered column in the WHERE clause throws an exception.

2019-01-23 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5109: --- Affects Version/s: 4.14.1 > Hinted local index with uncovered column in the WHERE clause

[jira] [Updated] (PHOENIX-5106) Avoid getting an explain plan for each query (even without tracing)

2019-01-22 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5106: --- Summary: Avoid getting an explain plan for each query (even without tracing) (was: Avoid

[jira] [Assigned] (PHOENIX-5106) Avoid geting an explain plan for each query (even without tracing)

2019-01-20 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-5106: -- Assignee: Lars Hofhansl > Avoid geting an explain plan for each query (even without

[jira] [Created] (PHOENIX-5106) Avoid geting an explain plan for each query (even without tracing)

2019-01-20 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5106: -- Summary: Avoid geting an explain plan for each query (even without tracing) Key: PHOENIX-5106 URL: https://issues.apache.org/jira/browse/PHOENIX-5106 Project:

[jira] [Updated] (PHOENIX-5106) Avoid geting an explain plan for each query (even without tracing)

2019-01-20 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5106: --- Attachment: 5106.txt > Avoid geting an explain plan for each query (even without tracing)

[jira] [Updated] (PHOENIX-5106) Avoid geting an explain plan for each query (even without tracing)

2019-01-20 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5106: --- Labels: performance (was: ) > Avoid geting an explain plan for each query (even without

[jira] [Updated] (PHOENIX-5104) PHOENIX-3547 breaks client backwards compatability

2019-01-18 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5104: --- Summary: PHOENIX-3547 breaks client backwards compatability (was: PHOENIX-3547 break

[jira] [Updated] (PHOENIX-5104) PHOENIX-3547 breaks client backwards compatability

2019-01-18 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5104: --- Fix Version/s: 4.15.0 > PHOENIX-3547 breaks client backwards compatability >

[jira] [Updated] (PHOENIX-5104) PHOENIX-3547 break client backwards compatability

2019-01-18 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5104: --- Description: Scenario: * New 4.15 client ** {{create table ns1.test (pk1 integer not null,

[jira] [Updated] (PHOENIX-5104) PHOENIX-3547 break client backwards compatability

2019-01-18 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5104: --- Affects Version/s: 4.15.0 > PHOENIX-3547 break client backwards compatability >

[jira] [Updated] (PHOENIX-5104) PHOENIX-3547 break client backwards compatability

2019-01-18 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5104: --- Description: Scenario: * New 4.15 client ** {{create table ns1.test (pk1 integer not null,

[jira] [Created] (PHOENIX-5104) PHOENIX-3547 break client backwards compatability

2019-01-18 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5104: -- Summary: PHOENIX-3547 break client backwards compatability Key: PHOENIX-5104 URL: https://issues.apache.org/jira/browse/PHOENIX-5104 Project: Phoenix

[jira] [Updated] (PHOENIX-5096) Local index region pruning is not working as expected.

2019-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5096: --- Description: The pruning of local indexes should do the following: * Use the local index *

[jira] [Updated] (PHOENIX-5096) Local index region pruning is not working as expected.

2019-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5096: --- Description: The pruning of local indexes should do the following: * Use the local index *

[jira] [Updated] (PHOENIX-5096) Local index region pruning is not working as expected.

2019-01-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5096: --- Description: The pruning of local indexes should do the following: * Use the local index *

[jira] [Created] (PHOENIX-5096) Local index region pruning is not working as expected.

2019-01-10 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5096: -- Summary: Local index region pruning is not working as expected. Key: PHOENIX-5096 URL: https://issues.apache.org/jira/browse/PHOENIX-5096 Project: Phoenix

[jira] [Updated] (PHOENIX-3740) Allow scanning of a main table only, skipping views

2019-01-09 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3740: --- Issue Type: New Feature (was: Bug) > Allow scanning of a main table only, skipping views

[jira] [Created] (PHOENIX-5090) Discuss: Allow transactional writes without buffering the entire transaction on the client.

2019-01-04 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5090: -- Summary: Discuss: Allow transactional writes without buffering the entire transaction on the client. Key: PHOENIX-5090 URL: https://issues.apache.org/jira/browse/PHOENIX-5090

[jira] [Updated] (PHOENIX-5090) Discuss: Allow transactional writes without buffering the entire transaction on the client.

2019-01-04 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5090: --- Description: Currently it is not possible execute transactions in Phoenix that are too

[jira] [Resolved] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2019-01-02 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-5084. Resolution: Fixed Fix Version/s: 4.14.2 4.15.0 Committed to

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2019-01-01 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Attachment: PHOENIX-5084-v4.txt > Changes from Transactional Tables are not visible to

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2019-01-01 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Attachment: PHOENIX-5084-v3.txt > Changes from Transactional Tables are not visible to

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-31 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Attachment: PHOENIX-5084-v2.txt > Changes from Transactional Tables are not visible to

[jira] [Assigned] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-30 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-5084: -- Assignee: Lars Hofhansl > Changes from Transactional Tables are not visible to

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-30 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Attachment: PHOENIX-5084.txt > Changes from Transactional Tables are not visible to query

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-29 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Description: Scenario: # Upsert and commit some data into a transactional table.

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-29 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Description: Scenario: # Upsert some data into a transactional table. (Autocommit or

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-29 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Description: Scenario: # Upsert some data into a transactional table. (Autocommit or

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-28 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Description: Scenario: # Upsert some data into a transactional table. # Query same table

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-28 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Priority: Blocker (was: Critical) > Changes from Transactional Tables are not visible to

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-28 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Affects Version/s: 4.15.0 4.14.1 > Changes from Transactional

[jira] [Updated] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5084: --- Description: Scenario: # Upsert some data into a transactional table. # Query same table

[jira] [Created] (PHOENIX-5084) Changes from Transactional Tables are not visible to query in different client

2018-12-27 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5084: -- Summary: Changes from Transactional Tables are not visible to query in different client Key: PHOENIX-5084 URL: https://issues.apache.org/jira/browse/PHOENIX-5084

[jira] [Updated] (PHOENIX-5082) Observations about the Phoenix-Omid integration

2018-12-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5082: --- Attachment: CommitTS-Sample.png > Observations about the Phoenix-Omid integration >

[jira] [Updated] (PHOENIX-5082) Observations about the Phoenix-Omid integration

2018-12-26 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5082: --- Attachment: Omid-sample.png Omid-profile.png > Observations about the

[jira] [Created] (PHOENIX-5082) Observations about the Phoenix-Omid integration

2018-12-26 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5082: -- Summary: Observations about the Phoenix-Omid integration Key: PHOENIX-5082 URL: https://issues.apache.org/jira/browse/PHOENIX-5082 Project: Phoenix

[jira] [Updated] (PHOENIX-5082) Observations about the Phoenix-Omid integration

2018-12-26 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5082: --- Description: Filing this issue to track my observations and perhaps some fixes. [~ohads]

[jira] [Updated] (PHOENIX-5082) Observations about the Phoenix-Omid integration

2018-12-26 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5082: --- Description: Filing this issue to track my observations and perhaps some fixes. >

[jira] [Updated] (PHOENIX-5074) DropTableWithViewsIT.testDropTableWithChildViews is flapping

2018-12-25 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5074: --- Attachment: 5074-addendum-1.4.patch > DropTableWithViewsIT.testDropTableWithChildViews is

[jira] [Reopened] (PHOENIX-4781) Phoenix client project's jar naming convention causes maven-deploy-plugin to fail

2018-11-30 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reopened PHOENIX-4781: > Phoenix client project's jar naming convention causes maven-deploy-plugin to > fail >

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-28 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Attachment: 5044-looksee-v3.txt > Remove server side mutation code from Phoenix >

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-28 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Description: This is for *discussion*. Perhaps controversial. It generally seems to be a

[jira] [Assigned] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-28 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-5044: -- Assignee: Lars Hofhansl > Remove server side mutation code from Phoenix >

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Attachment: 5044-looksee-v2.txt > Remove server side mutation code from Phoenix >

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Attachment: (was: 5044-looksee-v2.txt) > Remove server side mutation code from Phoenix

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Attachment: 5044-looksee-v2.txt > Remove server side mutation code from Phoenix >

[jira] [Updated] (PHOENIX-5045) Remove Global Mutable index code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5045: --- Description: In a continued effort to reduce Phoenix' complexity I propose that we remove

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Description: This is for *discussion*. Perhaps controversial. It generally seems to be a

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Attachment: 5044-looksee.txt > Remove server side mutation code from Phoenix >

[jira] [Created] (PHOENIX-5045) Remove Global Mutable index code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5045: -- Summary: Remove Global Mutable index code from Phoenix Key: PHOENIX-5045 URL: https://issues.apache.org/jira/browse/PHOENIX-5045 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5044: --- Description: This is for *discussion*. Perhaps controversial. It generally seems to be a

[jira] [Created] (PHOENIX-5044) Remove server side mutation code from Phoenix

2018-11-27 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5044: -- Summary: Remove server side mutation code from Phoenix Key: PHOENIX-5044 URL: https://issues.apache.org/jira/browse/PHOENIX-5044 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side mutations

2018-11-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5026: --- Comment: was deleted (was: Stupid question... Are the 4.x-HBase-1.1 and 4.x-HBase-0.98

[jira] [Resolved] (PHOENIX-5026) Add client setting to disable server side mutations

2018-11-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-5026. Resolution: Fixed Fix Version/s: 4.14.2 4.15.0 > Add client

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side mutations

2018-11-21 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5026: --- Summary: Add client setting to disable server side mutations (was: Add client setting to

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side deletes

2018-11-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5026: --- Attachment: 5026-withtests-v2.txt > Add client setting to disable server side deletes >

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side deletes

2018-11-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5026: --- Affects Version/s: 4.15.0 4.14.1 > Add client setting to disable

[jira] [Assigned] (PHOENIX-5026) Add client setting to disable server side deletes

2018-11-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-5026: -- Assignee: Lars Hofhansl > Add client setting to disable server side deletes >

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side deletes

2018-11-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5026: --- Attachment: 5026-withtests.txt > Add client setting to disable server side deletes >

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side deletes

2018-11-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5026: --- Attachment: 5026.txt > Add client setting to disable server side deletes >

[jira] [Created] (PHOENIX-5026) Add client setting to disable server side deletes

2018-11-16 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5026: -- Summary: Add client setting to disable server side deletes Key: PHOENIX-5026 URL: https://issues.apache.org/jira/browse/PHOENIX-5026 Project: Phoenix

[jira] [Created] (PHOENIX-5011) Straight DELETE FROM does not honor DISABLE_WAL setting on the table

2018-11-10 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5011: -- Summary: Straight DELETE FROM does not honor DISABLE_WAL setting on the table Key: PHOENIX-5011 URL: https://issues.apache.org/jira/browse/PHOENIX-5011 Project:

[jira] [Updated] (PHOENIX-5007) DELETE FROM times out - even with large HBase timeout setting

2018-11-08 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5007: --- Description: It seems there is currently no way to make a somewhat large DELETE FROM work

[jira] [Updated] (PHOENIX-5007) DELETE FROM times out - even with large HBase timeout setting

2018-11-08 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5007: --- Description: It seems there is currently no way to make a somewhat large DELETE FROM work

[jira] [Created] (PHOENIX-5007) DELETE FROM times out - even with large HBase timeout setting

2018-11-07 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-5007: -- Summary: DELETE FROM times out - even with large HBase timeout setting Key: PHOENIX-5007 URL: https://issues.apache.org/jira/browse/PHOENIX-5007 Project: Phoenix

[jira] [Updated] (PHOENIX-4995) Discreptany of internal cost estimation is EXPLAIN cost for HashJoins

2018-10-25 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4995: --- Description: In this case this was a SEMI with this plan: {code:java}

[jira] [Updated] (PHOENIX-4995) Discreptany of internal cost estimation is EXPLAIN cost for HashJoins

2018-10-25 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4995: --- Description: In this case this was a SEMI join of the form:   > Discreptany of internal

[jira] [Created] (PHOENIX-4995) Discreptany of internal cost estimation is EXPLAIN cost for HashJoins

2018-10-25 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-4995: -- Summary: Discreptany of internal cost estimation is EXPLAIN cost for HashJoins Key: PHOENIX-4995 URL: https://issues.apache.org/jira/browse/PHOENIX-4995 Project:

[jira] [Updated] (PHOENIX-4972) ORDER BY should use a GLOBAL index even if the query is not fully covered

2018-10-22 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4972: --- Attachment: PHOENIX-4972-4.x-HBase-1.4--not-working.patch > ORDER BY should use a GLOBAL

[jira] [Updated] (PHOENIX-4972) ORDER BY should use a GLOBAL index even if the query is not fully covered

2018-10-22 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4972: --- Attachment: PHOENIX-4972-4.x-HBase-1.4-v1.patch > ORDER BY should use a GLOBAL index even

[jira] [Resolved] (PHOENIX-4976) Comparisson on RVC are still incorrect

2018-10-22 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-4976. Resolution: Duplicate > Comparisson on RVC are still incorrect >

[jira] [Updated] (PHOENIX-4845) Support using Row Value Constructors in OFFSET clause to support paging in tables where the sort order of PK columns varies

2018-10-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4845: --- Attachment: PHOENIX-offset.txt > Support using Row Value Constructors in OFFSET clause to

[jira] [Updated] (PHOENIX-4845) Support using Row Value Constructors in OFFSET clause to support paging in tables where the sort order of PK columns varies

2018-10-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4845: --- Attachment: (was: PHOENIX-offset.txt) > Support using Row Value Constructors in OFFSET

[jira] [Updated] (PHOENIX-4845) Support using Row Value Constructors in OFFSET clause to support paging in tables where the sort order of PK columns varies

2018-10-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4845: --- Attachment: PHOENIX-offset.txt > Support using Row Value Constructors in OFFSET clause to

[jira] [Updated] (PHOENIX-4976) Comparisson on RVC are still incorrect

2018-10-16 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4976: --- Attachment: PHOENIX-4976-test.txt > Comparisson on RVC are still incorrect >

[jira] [Created] (PHOENIX-4976) Comparisson on RVC are still incorrect

2018-10-16 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-4976: -- Summary: Comparisson on RVC are still incorrect Key: PHOENIX-4976 URL: https://issues.apache.org/jira/browse/PHOENIX-4976 Project: Phoenix Issue Type:

[jira] [Updated] (PHOENIX-4972) ORDER BY should use a GLOBAL index even if the query is not fully covered

2018-10-14 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4972: --- Description: Like PHOENIX-4964 but for global indexes > ORDER BY should use a GLOBAL index

[jira] [Created] (PHOENIX-4972) ORDER BY should use a GLOBAL index even if the query is not fully covered

2018-10-14 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-4972: -- Summary: ORDER BY should use a GLOBAL index even if the query is not fully covered Key: PHOENIX-4972 URL: https://issues.apache.org/jira/browse/PHOENIX-4972

[jira] [Updated] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-12 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4967: --- Attachment: (was: PHOENIX-4967-4.x-HBase-1.4.v1.txt) > Reverse scan along LOCAL index

[jira] [Updated] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-12 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4967: --- Attachment: PHOENIX-4967-4.x-HBase-1.4.v1.txt > Reverse scan along LOCAL index does not

[jira] [Assigned] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-12 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-4967: -- Assignee: Lars Hofhansl > Reverse scan along LOCAL index does not always return all

[jira] [Updated] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-12 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4967: --- Attachment: PHOENIX-4967-4.x-HBase-1.4.v1.txt > Reverse scan along LOCAL index does not

[jira] [Updated] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-12 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4967: --- Description: Will attach a test-case soon. (Note that this independent of PHOENIX-4964)

[jira] [Updated] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-12 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Fix Version/s: 5.1.0 4.14.1 4.15.0 > ORDER BY should

[jira] [Updated] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4967: --- Attachment: PHOENIX-4967-test.txt > Reverse scan along LOCAL index does not always return

[jira] [Resolved] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-4964. Resolution: Fixed Committed to master and 4.x*(1.4, 1.3, 1.2) > ORDER BY should use a

[jira] [Created] (PHOENIX-4967) Reverse scan along LOCAL index does not always return all data

2018-10-11 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-4967: -- Summary: Reverse scan along LOCAL index does not always return all data Key: PHOENIX-4967 URL: https://issues.apache.org/jira/browse/PHOENIX-4967 Project:

[jira] [Updated] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Attachment: PHOENIX-4964-4.x-HBase-1.4.v4.txt > ORDER BY should use a LOCAL index even if

[jira] [Updated] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Attachment: (was: PHOENIX-4964-4.x-HBase-1.4.v4.txt) > ORDER BY should use a LOCAL

[jira] [Updated] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Attachment: PHOENIX-4964-4.x-HBase-1.4.v4.txt > ORDER BY should use a LOCAL index even if

[jira] [Updated] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Attachment: PHOENIX-4964-4.x-HBase-1.4.v3.txt > ORDER BY should use a LOCAL index even if

[jira] [Updated] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Summary: ORDER BY should use a LOCAL index even if the query is not fully covered (was:

[jira] [Assigned] (PHOENIX-4964) ORDER BY should use a LOCAL index even if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-4964: -- Assignee: Lars Hofhansl > ORDER BY should use a LOCAL index even if the query is

[jira] [Resolved] (PHOENIX-4965) Phoenix should issue a reverse HBase for ORDER BY DESC along an index.

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-4965. Resolution: Invalid NM. This had to do with the fact the column was nullable. For a

[jira] [Updated] (PHOENIX-4964) ORDER BY does not use an index if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Attachment: PHOENIX-4964-4.x-HBase-1.4.v2.txt > ORDER BY does not use an index if the

[jira] [Updated] (PHOENIX-4964) ORDER BY does not use an index if the query is not fully covered

2018-10-11 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Attachment: PHOENIX-4964-4.x-HBase-1.4.txt > ORDER BY does not use an index if the query

[jira] [Created] (PHOENIX-4965) Phoenix should issue a reverse HBase for ORDER BY DESC along an index.

2018-10-11 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-4965: -- Summary: Phoenix should issue a reverse HBase for ORDER BY DESC along an index. Key: PHOENIX-4965 URL: https://issues.apache.org/jira/browse/PHOENIX-4965

[jira] [Updated] (PHOENIX-4964) ORDER BY does not use an index if the query is not fully covered

2018-10-10 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4964: --- Priority: Minor (was: Major) > ORDER BY does not use an index if the query is not fully

[jira] [Created] (PHOENIX-4964) ORDER BY does not use an index if the query is not fully covered

2018-10-10 Thread Lars Hofhansl (JIRA)
Lars Hofhansl created PHOENIX-4964: -- Summary: ORDER BY does not use an index if the query is not fully covered Key: PHOENIX-4964 URL: https://issues.apache.org/jira/browse/PHOENIX-4964 Project:

[jira] [Resolved] (PHOENIX-4939) It takes over 13 seconds to create a local index on an empty table

2018-10-05 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-4939. Resolution: Invalid > It takes over 13 seconds to create a local index on an empty table

<    5   6   7   8   9   10   11   12   13   14   >