[jira] [Comment Edited] (PHOENIX-4289) UPDATE STATISTICS command does not collect stats for local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213608#comment-16213608 ] Samarth Jain edited comment on PHOENIX-4289 at 10/21/17 12:58 AM: -- I

[jira] [Commented] (PHOENIX-4289) UPDATE STATISTICS command does not collect stats for local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213608#comment-16213608 ] Samarth Jain commented on PHOENIX-4289: --- I think I see what is going on. When a table has an

[jira] [Commented] (PHOENIX-4289) UPDATE STATISTICS command does not collect stats for local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213580#comment-16213580 ] Samarth Jain commented on PHOENIX-4289: --- [~mujtabachohan], I am unable to repro this issue in a

[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=16213562#comment-16213562 ] Hadoop QA commented on PHOENIX-4237: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Comment Edited] (PHOENIX-3999) Optimize inner joins as SKIP-SCAN-JOIN when possible

[ https://issues.apache.org/jira/browse/PHOENIX-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213415#comment-16213415 ] Will Dumaresq edited comment on PHOENIX-3999 at 10/20/17 10:35 PM: ---

[jira] [Commented] (PHOENIX-3999) Optimize inner joins as SKIP-SCAN-JOIN when possible

[ https://issues.apache.org/jira/browse/PHOENIX-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213415#comment-16213415 ] Will Dumaresq commented on PHOENIX-3999: The query pattern is: {code:java} do { SELECT

[jira] [Commented] (PHOENIX-3999) Optimize inner joins as SKIP-SCAN-JOIN when possible

[ https://issues.apache.org/jira/browse/PHOENIX-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213334#comment-16213334 ] James Taylor commented on PHOENIX-3999: --- Thanks, [~wdumaresq]. So from the outer query you collect

[jira] [Assigned] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4148: - Assignee: Lars Hofhansl > COUNT(DISTINCT(...)) should have a memory size limit >

[jira] [Updated] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4148: -- Fix Version/s: 4.13.0 > COUNT(DISTINCT(...)) should have a memory size limit >

[jira] [Commented] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit

[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213321#comment-16213321 ] James Taylor commented on PHOENIX-4148: --- [~lhofhansl] - I think the patch is fine. I'm fine if you

[jira] [Commented] (PHOENIX-3999) Optimize inner joins as SKIP-SCAN-JOIN when possible

[ https://issues.apache.org/jira/browse/PHOENIX-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213295#comment-16213295 ] Will Dumaresq commented on PHOENIX-3999: Hi [~jamestaylor], The original use case was to be

[jira] [Updated] (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:all-tabpanel ] Shehzaad Nakhoda updated PHOENIX-4237: -- Attachment: PHOENIX-4237_v2.patch This patch fixes the test failure caused by an JDK

[jira] [Created] (PHOENIX-4314) Use bytes scanned to drive join order

James Taylor created PHOENIX-4314: - Summary: Use bytes scanned to drive join order Key: PHOENIX-4314 URL: https://issues.apache.org/jira/browse/PHOENIX-4314 Project: Phoenix Issue Type:

[jira] [Updated] (PHOENIX-4288) Indexes not used when ordering by primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4288: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-4313 > Indexes not used when

[jira] [Updated] (PHOENIX-1555) Fallback to many-to-many join if hash join fails due to insufficient memory

[ https://issues.apache.org/jira/browse/PHOENIX-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1555: -- Issue Type: Bug (was: Sub-task) Parent: (was: PHOENIX-1167) > Fallback to

[jira] [Updated] (PHOENIX-1555) Fallback to many-to-many join if hash join fails due to insufficient memory

[ https://issues.apache.org/jira/browse/PHOENIX-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1555: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-4313 > Fallback to many-to-many join

[jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1556: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-4313 > Base hash versus sort merge

[jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1556: -- Issue Type: Bug (was: Sub-task) Parent: (was: PHOENIX-4313) > Base hash versus

[jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1556: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-4313 > Base hash versus sort merge

[jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1556: -- Issue Type: Bug (was: Sub-task) Parent: (was: PHOENIX-1167) > Base hash versus

[jira] [Created] (PHOENIX-4313) Use the bytes scanned to drive optimizer decisions

James Taylor created PHOENIX-4313: - Summary: Use the bytes scanned to drive optimizer decisions Key: PHOENIX-4313 URL: https://issues.apache.org/jira/browse/PHOENIX-4313 Project: Phoenix

[jira] [Resolved] (PHOENIX-4312) Choose between sort merge and hash join based on size of scanned data

[ https://issues.apache.org/jira/browse/PHOENIX-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4312. --- Resolution: Duplicate Duplicate of PHOENIX-1556 > Choose between sort merge and hash join

[jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1556: -- Labels: CostBasedOptimization (was: calcite) > Base hash versus sort merge join decision on

[jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned

[ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1556: -- Summary: Base hash versus sort merge join decision on how much data will be scanned (was:

[jira] [Updated] (PHOENIX-4312) Choose between sort merge and hash join based on size of scanned data

[ https://issues.apache.org/jira/browse/PHOENIX-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4312: -- Labels: CostBasedOptimization (was: ) > Choose between sort merge and hash join based on

[jira] [Created] (PHOENIX-4312) Choose between sort merge and hash join based on size of scanned data

James Taylor created PHOENIX-4312: - Summary: Choose between sort merge and hash join based on size of scanned data Key: PHOENIX-4312 URL: https://issues.apache.org/jira/browse/PHOENIX-4312 Project:

[jira] [Commented] (PHOENIX-1555) Fallback to many-to-many join if hash join fails due to insufficient memory

[ https://issues.apache.org/jira/browse/PHOENIX-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213219#comment-16213219 ] James Taylor commented on PHOENIX-1555: --- This would be a good one to get back to, [~maryannxue].

[jira] [Commented] (PHOENIX-3050) Handle DESC columns in child/parent join optimization

[ https://issues.apache.org/jira/browse/PHOENIX-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213210#comment-16213210 ] James Taylor commented on PHOENIX-3050: --- Would be great to get back to this one, [~maryannxue] if

[jira] [Commented] (PHOENIX-4311) Support UNNEST over ARRAY data type

[ https://issues.apache.org/jira/browse/PHOENIX-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213204#comment-16213204 ] James Taylor commented on PHOENIX-4311: --- WDYT, [~maryannxue] - would you have some spare cycles

[jira] [Commented] (PHOENIX-4310) Remove unnecessary casts in UngroupedAggregateRegionObserverIT

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

[jira] [Updated] (PHOENIX-4288) Indexes not used when ordering by primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4288: -- Labels: CostBasedOptimization (was: ) > Indexes not used when ordering by primary key >

[jira] [Assigned] (PHOENIX-4311) Support UNNEST over ARRAY data type

[ https://issues.apache.org/jira/browse/PHOENIX-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4311: - Assignee: (was: Maryann Xue) > Support UNNEST over ARRAY data type >

[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=16213201#comment-16213201 ] Hudson commented on PHOENIX-4280: - FAILURE: Integrated in Jenkins build Phoenix-master #1846 (See

[jira] [Commented] (PHOENIX-4288) Indexes not used when ordering by primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213200#comment-16213200 ] James Taylor commented on PHOENIX-4288: --- [~maryannxue] - this would be a good one for you if you

[jira] [Updated] (PHOENIX-4288) Indexes not used when ordering by primary key

[ https://issues.apache.org/jira/browse/PHOENIX-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4288: -- Summary: Indexes not used when ordering by primary key (was: Indexes not used when ordering

[jira] [Commented] (PHOENIX-3999) Optimize inner joins as SKIP-SCAN-JOIN when possible

[ https://issues.apache.org/jira/browse/PHOENIX-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213191#comment-16213191 ] James Taylor commented on PHOENIX-3999: --- I believe in this case the user is holding

[jira] [Created] (PHOENIX-4311) Support UNNEST over ARRAY data type

James Taylor created PHOENIX-4311: - Summary: Support UNNEST over ARRAY data type Key: PHOENIX-4311 URL: https://issues.apache.org/jira/browse/PHOENIX-4311 Project: Phoenix Issue Type: Test

[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=16213121#comment-16213121 ] Hadoop QA commented on PHOENIX-4237: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-4277) Treat delete markers consistently with puts for point-in-time scans

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

[jira] [Updated] (PHOENIX-4277) Treat delete markers consistently with puts for point-in-time scans

[ https://issues.apache.org/jira/browse/PHOENIX-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4277: -- Attachment: PHOENIX-4277_v3.patch [~vincentpoon] - how about adding a test for the index

[jira] [Assigned] (PHOENIX-4277) Treat delete markers consistently with puts for point-in-time scans

[ https://issues.apache.org/jira/browse/PHOENIX-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4277: - Assignee: James Taylor (was: Vincent Poon) > Treat delete markers consistently with

[jira] [Updated] (PHOENIX-4277) Treat delete markers consistently with puts for point-in-time scans

[ https://issues.apache.org/jira/browse/PHOENIX-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4277: -- Fix Version/s: 4.13.0 > Treat delete markers consistently with puts for point-in-time scans >

[jira] [Resolved] (PHOENIX-4310) Remove unnecessary casts in UngroupedAggregateRegionObserverIT

[ https://issues.apache.org/jira/browse/PHOENIX-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4310. --- Resolution: Fixed Fix Version/s: 4.13.0 FYI, [~vincentpoon]. > Remove unnecessary

[jira] [Created] (PHOENIX-4310) Remove unnecessary casts in UngroupedAggregateRegionObserverIT

James Taylor created PHOENIX-4310: - Summary: Remove unnecessary casts in UngroupedAggregateRegionObserverIT Key: PHOENIX-4310 URL: https://issues.apache.org/jira/browse/PHOENIX-4310 Project: Phoenix

[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=16213058#comment-16213058 ] Thomas D'Silva commented on PHOENIX-4280: - +1 LGTM > Delete doesn't work when immutable indexes

Re: [DISCUSS] Road to HBase 2.0.0

Thanks James! On Wed, Oct 18, 2017 at 3:52 PM, James Taylor wrote: > FYI, I filed JIRAs for the Phoenix changes we talked about in the > spreadsheet and labeled them all with HBase-2.0 [1]. > > [1] >

[jira] [Updated] (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:all-tabpanel ] James Taylor updated PHOENIX-4237: -- Attachment: PHOENIX-4237_v1.patch [~shehzaadn] - here's your patch with a couple of minor

[jira] [Assigned] (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:all-tabpanel ] James Taylor reassigned PHOENIX-4237: - Assignee: Shehzaad Nakhoda > Allow sorting on (Java) collation keys for non-English

[jira] [Commented] (PHOENIX-4139) select distinct with identical aggregations return weird values

[ https://issues.apache.org/jira/browse/PHOENIX-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212872#comment-16212872 ] James Taylor commented on PHOENIX-4139: --- Sounds like you're honing in on the root cause,

[jira] [Commented] (PHOENIX-4139) select distinct with identical aggregations return weird values

[ https://issues.apache.org/jira/browse/PHOENIX-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212859#comment-16212859 ] Csaba Skrabak commented on PHOENIX-4139: If you modify the select like this: select distinct

[jira] [Comment Edited] (PHOENIX-4139) select distinct with identical aggregations return weird values

[ https://issues.apache.org/jira/browse/PHOENIX-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212846#comment-16212846 ] Csaba Skrabak edited comment on PHOENIX-4139 at 10/20/17 4:32 PM: -- The

[jira] [Commented] (PHOENIX-4139) select distinct with identical aggregations return weird values

[ https://issues.apache.org/jira/browse/PHOENIX-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212846#comment-16212846 ] Csaba Skrabak commented on PHOENIX-4139: The NUL-separated value is generated 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_v12.patch Attaching final version of patch. Only difference with

[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=16212836#comment-16212836 ] James Taylor commented on PHOENIX-4280: --- [~tdsilva] - last patch (v11) passes all unit tests

[jira] [Updated] (PHOENIX-4309) Cannot use IndexTool to populate index table when indexed column contains periods.

[ https://issues.apache.org/jira/browse/PHOENIX-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Januszkiewicz updated PHOENIX-4309: -- Description: Table DDL: {code:sql} create table t( rowkey VARCHAR;

[jira] [Updated] (PHOENIX-4308) Cannot use IndexTool to populate index table when using a functional index on non-default column family.

[ https://issues.apache.org/jira/browse/PHOENIX-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Januszkiewicz updated PHOENIX-4308: -- Description: Table DDL: {code:sql} create table t( rowkey VARCHAR PRIMARY

[jira] [Updated] (PHOENIX-4307) Cannot create index on column without specifying column family if the column family is lowercase.

[ https://issues.apache.org/jira/browse/PHOENIX-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcin Januszkiewicz updated PHOENIX-4307: -- Description: Table DDL: {code:sql} create table t ( rowkey VARCHAR

[jira] [Created] (PHOENIX-4309) Cannot use IndexTool to populate index table when indexed column contains periods.

Marcin Januszkiewicz created PHOENIX-4309: - Summary: Cannot use IndexTool to populate index table when indexed column contains periods. Key: PHOENIX-4309 URL:

[jira] [Created] (PHOENIX-4308) Cannot use IndexTool to populate index table when using a functional index on non-default column family.

Marcin Januszkiewicz created PHOENIX-4308: - Summary: Cannot use IndexTool to populate index table when using a functional index on non-default column family. Key: PHOENIX-4308 URL:

[jira] [Created] (PHOENIX-4307) Cannot create index on column without specifying column family if the column family is lowercase.

Marcin Januszkiewicz created PHOENIX-4307: - Summary: Cannot create index on column without specifying column family if the column family is lowercase. Key: PHOENIX-4307 URL:

[GitHub] phoenix pull request #276: update

Github user ChPi closed the pull request at: https://github.com/apache/phoenix/pull/276 ---

[GitHub] phoenix pull request #276: update

GitHub user ChPi opened a pull request: https://github.com/apache/phoenix/pull/276 update cdh You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChPi/phoenix 4.11-HBase-1.2 Alternatively you can review and apply these changes as

[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=16212312#comment-16212312 ] Hadoop QA commented on PHOENIX-4280: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (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 q

[ https://issues.apache.org/jira/browse/PHOENIX-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212276#comment-16212276 ] James Taylor commented on PHOENIX-4167: --- If you set {{hasSeparatorByte}} does it work correctly,