[jira] [Assigned] (PHOENIX-4160) research for a proper hash size set for APPROX_COUNT_DISTINCT

[ https://issues.apache.org/jira/browse/PHOENIX-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang reassigned PHOENIX-4160: --- Assignee: Ethan Wang > research for a proper hash size set for APPROX_COUNT_DISTINCT >

[jira] [Commented] (PHOENIX-4164) APPROX_COUNT_DISTINCT becomes imprecise at 20m unique values.

[ https://issues.apache.org/jira/browse/PHOENIX-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159770#comment-16159770 ] Ethan Wang commented on PHOENIX-4164: - I see. sounds good. I make this related to PHOENIX-4160 so

[jira] [Resolved] (PHOENIX-4164) APPROX_COUNT_DISTINCT becomes imprecise at 20m unique values.

[ https://issues.apache.org/jira/browse/PHOENIX-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-4164. Resolution: Invalid Had to do with how I ran my test... Sorry for the noise. >

[jira] [Assigned] (PHOENIX-4164) APPROX_COUNT_DISTINCT becomes imprecise at 20m unique values.

[ https://issues.apache.org/jira/browse/PHOENIX-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-4164: -- Assignee: (was: Ethan Wang) > APPROX_COUNT_DISTINCT becomes imprecise at 20m

[jira] [Commented] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

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

[jira] [Commented] (PHOENIX-4189) Avoid direct use of ObjectInputStream in Hive integration

[ https://issues.apache.org/jira/browse/PHOENIX-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159740#comment-16159740 ] Josh Elser commented on PHOENIX-4189: - The static inner-class LookAheadObjectInputStream on

[jira] [Commented] (PHOENIX-4189) Avoid direct use of ObjectInputStream in Hive integration

[ https://issues.apache.org/jira/browse/PHOENIX-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159743#comment-16159743 ] Josh Elser commented on PHOENIX-4189: - FYI [~sergey.soldatov] > Avoid direct use of

[jira] [Updated] (PHOENIX-4189) Avoid direct use of ObjectInputStream in Hive integration

[ https://issues.apache.org/jira/browse/PHOENIX-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-4189: Attachment: PHOENIX-4189.001.patch > Avoid direct use of ObjectInputStream in Hive integration >

[jira] [Updated] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

[ https://issues.apache.org/jira/browse/PHOENIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-4188: Attachment: PHOENIX-4188.001.patch > Disable DTD parsing on Pherf XML documents >

[jira] [Updated] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

[ https://issues.apache.org/jira/browse/PHOENIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-4188: Attachment: (was: PHOENIX-4188.001.patch) > Disable DTD parsing on Pherf XML documents >

[jira] [Commented] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

[ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159726#comment-16159726 ] Lars Hofhansl commented on PHOENIX-4165: I wonder whether we can hide HBase dependencies in

[jira] [Created] (PHOENIX-4189) Avoid direct use of ObjectInputStream in Hive integration

Josh Elser created PHOENIX-4189: --- Summary: Avoid direct use of ObjectInputStream in Hive integration Key: PHOENIX-4189 URL: https://issues.apache.org/jira/browse/PHOENIX-4189 Project: Phoenix

[jira] [Commented] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

[ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159715#comment-16159715 ] James Taylor commented on PHOENIX-4165: --- +1 to your patch. Thanks for the contribution,

[jira] [Commented] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

[ https://issues.apache.org/jira/browse/PHOENIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159707#comment-16159707 ] James Taylor commented on PHOENIX-4188: --- [~mujtabachohan]? > Disable DTD parsing on Pherf XML

[jira] [Commented] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

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

[jira] [Updated] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

[ https://issues.apache.org/jira/browse/PHOENIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-4188: Attachment: PHOENIX-4188.001.patch > Disable DTD parsing on Pherf XML documents >

[jira] [Commented] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

[ https://issues.apache.org/jira/browse/PHOENIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159683#comment-16159683 ] Josh Elser commented on PHOENIX-4188: - Also, getting it seems like Pherf is a little worse for wear

[jira] [Created] (PHOENIX-4188) Disable DTD parsing on Pherf XML documents

Josh Elser created PHOENIX-4188: --- Summary: Disable DTD parsing on Pherf XML documents Key: PHOENIX-4188 URL: https://issues.apache.org/jira/browse/PHOENIX-4188 Project: Phoenix Issue Type: Bug

[jira] [Commented] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

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

[jira] [Commented] (PHOENIX-4150) Adding a policy filter to whitelist the properties that allow to be passed to Phoenix

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

[jira] [Commented] (PHOENIX-4186) Modify NativeHBaseTypesIT to not use CurrentSCN

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

[jira] [Updated] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

[ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4165: --- Attachment: 4165-4.x-HBase-0.98.txt 4x.0.98 patch. There seem to be subtle differences

[jira] [Resolved] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

[ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-4187. --- Resolution: Fixed Turns out this is not an issue. When we don't use the server timestamp,

[jira] [Created] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified

Samarth Jain created PHOENIX-4187: - Summary: Use server timestamp for ROW_TIMESTAMP column when value is not specified Key: PHOENIX-4187 URL: https://issues.apache.org/jira/browse/PHOENIX-4187

[jira] [Commented] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

[ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159481#comment-16159481 ] Lars Hofhansl commented on PHOENIX-4165: Thanks. I found the test-runs kinda unstable. One time

[jira] [Commented] (PHOENIX-4186) Modify NativeHBaseTypesIT to not use CurrentSCN

[ https://issues.apache.org/jira/browse/PHOENIX-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159480#comment-16159480 ] James Taylor commented on PHOENIX-4186: --- You'll need to change the test to not use HBASE_NATIVE as

[jira] [Updated] (PHOENIX-4186) Modify NativeHBaseTypesIT to not use CurrentSCN

[ https://issues.apache.org/jira/browse/PHOENIX-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4186: Attachment: PHOENIX-4186.patch [~jamestaylor] Can you please review? > Modify

[jira] [Created] (PHOENIX-4186) Modify NativeHBaseTypesIT to not use CurrentSCN

Thomas D'Silva created PHOENIX-4186: --- Summary: Modify NativeHBaseTypesIT to not use CurrentSCN Key: PHOENIX-4186 URL: https://issues.apache.org/jira/browse/PHOENIX-4186 Project: Phoenix

[jira] [Commented] (PHOENIX-4150) Adding a policy filter to whitelist the properties that allow to be passed to Phoenix

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

[jira] [Commented] (PHOENIX-4184) Reduce flappiness of FlappingAlterTableIT

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

[jira] [Commented] (PHOENIX-4150) Adding a policy filter to whitelist the properties that allow to be passed to Phoenix

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

[jira] [Created] (PHOENIX-4185) converting tests for disable DDL/DML for 4.12

Ethan Wang created PHOENIX-4185: --- Summary: converting tests for disable DDL/DML for 4.12 Key: PHOENIX-4185 URL: https://issues.apache.org/jira/browse/PHOENIX-4185 Project: Phoenix Issue Type:

[jira] [Commented] (PHOENIX-4138) Create a hard limit on number of indexes per table

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

[jira] [Commented] (PHOENIX-4003) Document how to use snapshots for MR

[ https://issues.apache.org/jira/browse/PHOENIX-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159252#comment-16159252 ] Akshita Malhotra commented on PHOENIX-4003: --- [~pconrad] I will create the first draft

[jira] [Commented] (PHOENIX-4161) TableSnapshotReadsMapReduceIT shouldn't need to run its own mini cluster

[ https://issues.apache.org/jira/browse/PHOENIX-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159250#comment-16159250 ] Akshita Malhotra commented on PHOENIX-4161: --- Looking into the issue. >

[jira] [Updated] (PHOENIX-4150) Adding a policy filter to whitelist the properties that allow to be passed to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang updated PHOENIX-4150: Attachment: PHOENIX-4150-v4-nit.patch Adding headers for apache license for the new included

[jira] [Commented] (PHOENIX-4179) Use max timestamp of projected cells for cell timestamp returned to client

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

[jira] [Commented] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

[ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159159#comment-16159159 ] Samarth Jain commented on PHOENIX-4165: --- [~lhofhansl] - I am seeing that the test runs didn't

[jira] [Commented] (PHOENIX-4138) Create a hard limit on number of indexes per table

[ https://issues.apache.org/jira/browse/PHOENIX-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159156#comment-16159156 ] churro morales commented on PHOENIX-4138: - I can extract a code block to unit test this, that

[jira] [Commented] (PHOENIX-4165) Do not wait no new memory chunk can be allocated

[ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159150#comment-16159150 ] Lars Hofhansl commented on PHOENIX-4165: Aside from a test run with 0.98, any further comments?

[jira] [Commented] (PHOENIX-4150) Adding a policy filter to whitelist the properties that allow to be passed to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159100#comment-16159100 ] Thomas D'Silva commented on PHOENIX-4150: - +1 > Adding a policy filter to whitelist the

[jira] [Resolved] (PHOENIX-4184) Reduce flappiness of FlappingAlterTableIT

[ https://issues.apache.org/jira/browse/PHOENIX-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-4184. --- Resolution: Fixed Fix Version/s: 4.12.0 > Reduce flappiness of FlappingAlterTableIT

[jira] [Updated] (PHOENIX-4184) Reduce flappiness of FlappingAlterTableIT

[ https://issues.apache.org/jira/browse/PHOENIX-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-4184: -- Attachment: PHOENIX-4184.patch > Reduce flappiness of FlappingAlterTableIT >

[jira] [Created] (PHOENIX-4184) Reduce flappiness of FlappingAlterTableIT

Samarth Jain created PHOENIX-4184: - Summary: Reduce flappiness of FlappingAlterTableIT Key: PHOENIX-4184 URL: https://issues.apache.org/jira/browse/PHOENIX-4184 Project: Phoenix Issue Type:

[jira] [Commented] (PHOENIX-4138) Create a hard limit on number of indexes per table

[ https://issues.apache.org/jira/browse/PHOENIX-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159064#comment-16159064 ] James Taylor commented on PHOENIX-4138: --- Patch looks good, but we need a test that hits the limit.

[jira] [Created] (PHOENIX-4183) Disallow creating mutable indexes on tables with ROW_TIMESTAMP column

Samarth Jain created PHOENIX-4183: - Summary: Disallow creating mutable indexes on tables with ROW_TIMESTAMP column Key: PHOENIX-4183 URL: https://issues.apache.org/jira/browse/PHOENIX-4183 Project:

[jira] [Updated] (PHOENIX-4138) Create a hard limit on number of indexes per table

[ https://issues.apache.org/jira/browse/PHOENIX-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] churro morales updated PHOENIX-4138: Attachment: PHOENIX-4138.patch attached is the master patch, if you guys are good with

[jira] [Commented] (PHOENIX-4179) Use max timestamp of projected cells for cell timestamp returned to client

[ https://issues.apache.org/jira/browse/PHOENIX-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158970#comment-16158970 ] Vincent Poon commented on PHOENIX-4179: --- looks good [~jamestaylor], +1 > Use max timestamp of

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

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

[GitHub] phoenix issue #268: PHOENIX-4010 Hash Join cache may not be send to all regi...

Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/268 +1 ---

[jira] [Commented] (PHOENIX-4010) Hash Join cache may not be send to all regionservers when we have stale HBase meta cache

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

[GitHub] phoenix issue #268: PHOENIX-4010 Hash Join cache may not be send to all regi...

Github user ankitsinghal commented on the issue: https://github.com/apache/phoenix/pull/268 Thanks @JamesRTaylor , have taken care the review comments in latest commit. Let me know if it is fine now ---

[jira] [Created] (PHOENIX-4182) While using DatabaseMetaData.getTables(catalog,schemaPattern,tableNamePattern,types[]) throwing exception for getting SEQUENCE information.

suraj misra created PHOENIX-4182: Summary: While using DatabaseMetaData.getTables(catalog,schemaPattern,tableNamePattern,types[]) throwing exception for getting SEQUENCE information. Key: PHOENIX-4182 URL:

[jira] [Commented] (PHOENIX-4182) While using DatabaseMetaData.getTables(catalog,schemaPattern,tableNamePattern,types[]) throwing exception for getting SEQUENCE information.

[ https://issues.apache.org/jira/browse/PHOENIX-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158536#comment-16158536 ] suraj misra commented on PHOENIX-4182: -- Please let me know if you need any other information >