[jira] [Commented] (PHOENIX-3685) Extra DeleteFamily marker in non tx index table when setting covered column to null

[ https://issues.apache.org/jira/browse/PHOENIX-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884095#comment-15884095 ] James Taylor commented on PHOENIX-3685: --- That sounds like the root cause, [~tdsilva]. Is it easy

[jira] [Resolved] (PHOENIX-3690) Support declaring default values in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla resolved PHOENIX-3690. -- Resolution: Fixed > Support declaring default values in

[jira] [Updated] (PHOENIX-3690) Support declaring default values in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3690: - Attachment: PHOENIX-3690_v2.patch Here is the patch addresses reviews

[jira] [Commented] (PHOENIX-3690) Support declaring default values in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883983#comment-15883983 ] Kevin Liew commented on PHOENIX-3690: - I suggest we set PhoenixSchema.typeFactory and

[jira] [Commented] (PHOENIX-3685) Extra DeleteFamily marker in non tx index table when setting covered column to null

[ https://issues.apache.org/jira/browse/PHOENIX-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883954#comment-15883954 ] Thomas D'Silva commented on PHOENIX-3685: - I think this happens because we always generate a

[jira] [Updated] (PHOENIX-3695) CaseStatementIT#testUnfoundSingleColumnCaseStatement is failing on encode columns branch

[ https://issues.apache.org/jira/browse/PHOENIX-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3695: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-1598 >

[jira] [Created] (PHOENIX-3695) CaseStatementIT#testUnfoundSingleColumnCaseStatement is failing on encode columns branch

Samarth Jain created PHOENIX-3695: - Summary: CaseStatementIT#testUnfoundSingleColumnCaseStatement is failing on encode columns branch Key: PHOENIX-3695 URL: https://issues.apache.org/jira/browse/PHOENIX-3695

[jira] [Commented] (PHOENIX-3695) CaseStatementIT#testUnfoundSingleColumnCaseStatement is failing on encode columns branch

[ https://issues.apache.org/jira/browse/PHOENIX-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883918#comment-15883918 ] Samarth Jain commented on PHOENIX-3695: --- This test seems to be failing for immutable indexes. Need

[jira] [Updated] (PHOENIX-3649) After PHOENIX-3271 higher memory consumption on RS leading to OOM/abort on immutable index creation with multiple regions on single RS

[ https://issues.apache.org/jira/browse/PHOENIX-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3649: -- Priority: Blocker (was: Major) > After PHOENIX-3271 higher memory consumption on RS leading

[jira] [Assigned] (PHOENIX-3649) After PHOENIX-3271 higher memory consumption on RS leading to OOM/abort on immutable index creation with multiple regions on single RS

[ https://issues.apache.org/jira/browse/PHOENIX-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3649: - Assignee: Ankit Singhal > After PHOENIX-3271 higher memory consumption on RS leading

[jira] [Commented] (PHOENIX-3649) After PHOENIX-3271 higher memory consumption on RS leading to OOM/abort on immutable index creation with multiple regions on single RS

[ https://issues.apache.org/jira/browse/PHOENIX-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883829#comment-15883829 ] Mujtaba Chohan commented on PHOENIX-3649: - [~an...@apache.org] Just checking when can we expect

[jira] [Commented] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns

[ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883723#comment-15883723 ] James Taylor commented on PHOENIX-3667: --- +1. Looks great, [~samarthjain]. > Optimize

[jira] [Updated] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns

[ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3667: -- Attachment: PHOENIX-3667_v2.patch Thanks for the reviews, [~jamestaylor]. Updated patch with

[jira] [Commented] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns

[ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883678#comment-15883678 ] James Taylor commented on PHOENIX-3667: --- This looks good, except for the

[jira] [Updated] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns

[ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3667: -- Attachment: WhereClause.jpg My first perf test was to track query performance as we increase

[jira] [Commented] (PHOENIX-3694) Drop schema does not invalidate schema from the server cache

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

[jira] [Updated] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns

[ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3667: -- Attachment: PHOENIX-3667.patch Updated patch with review comments. I also added a new filter

[jira] [Commented] (PHOENIX-3663) Implement resource controls in Phoenix JDBC driver

[ https://issues.apache.org/jira/browse/PHOENIX-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883612#comment-15883612 ] James Taylor commented on PHOENIX-3663: --- +1. LGTM. Thanks, [~gjacoby]! > Implement resource

[jira] [Updated] (PHOENIX-3663) Implement resource controls in Phoenix JDBC driver

[ https://issues.apache.org/jira/browse/PHOENIX-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-3663: - Attachment: PHOENIX-3663.v2.patch Minor revision to patch to use

[jira] [Commented] (PHOENIX-3694) Drop schema does not invalidate schema from the server cache

[ https://issues.apache.org/jira/browse/PHOENIX-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883457#comment-15883457 ] Sergey Soldatov commented on PHOENIX-3694: -- LGTM except the incorrect indentation (tabs are

[jira] [Commented] (PHOENIX-3663) Implement resource controls in Phoenix JDBC driver

[ https://issues.apache.org/jira/browse/PHOENIX-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883451#comment-15883451 ] James Taylor commented on PHOENIX-3663: --- Patch looks good, [~gjacoby]. One minor issue: - Instead

[jira] [Updated] (PHOENIX-3694) Drop schema does not invalidate schema from the server cache

[ https://issues.apache.org/jira/browse/PHOENIX-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3694: --- Attachment: PHOENIX-3694.patch > Drop schema does not invalidate schema from the server

[jira] [Created] (PHOENIX-3694) Drop schema does not invalidate schema from the server cache

Ankit Singhal created PHOENIX-3694: -- Summary: Drop schema does not invalidate schema from the server cache Key: PHOENIX-3694 URL: https://issues.apache.org/jira/browse/PHOENIX-3694 Project: Phoenix

[jira] [Commented] (PHOENIX-3686) De-couple PQS's use of Kerberos to talk to HBase and client authentication

[ https://issues.apache.org/jira/browse/PHOENIX-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883421#comment-15883421 ] Josh Elser commented on PHOENIX-3686: - Actually, I should add a unit test for this one too. Should

[jira] [Commented] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns

[ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883416#comment-15883416 ] James Taylor commented on PHOENIX-3667: --- A few minor nits on patch for

[jira] [Updated] (PHOENIX-3693) Update to Tephra 0.11.0

[ https://issues.apache.org/jira/browse/PHOENIX-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3693: -- Fix Version/s: 4.10.0 > Update to Tephra 0.11.0 > --- > >

[jira] [Created] (PHOENIX-3693) Update to Tephra 0.11.0

James Taylor created PHOENIX-3693: - Summary: Update to Tephra 0.11.0 Key: PHOENIX-3693 URL: https://issues.apache.org/jira/browse/PHOENIX-3693 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-3663) Implement resource controls in Phoenix JDBC driver

[ https://issues.apache.org/jira/browse/PHOENIX-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-3663: - Attachment: PHOENIX-3663.patch Patch to create an optional per-ConnectionQueryServices

[jira] [Comment Edited] (PHOENIX-3689) Not determinist order by with limit

[ https://issues.apache.org/jira/browse/PHOENIX-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882399#comment-15882399 ] chenglei edited comment on PHOENIX-3689 at 2/24/17 10:27 AM: - Thank your for

[jira] [Comment Edited] (PHOENIX-3689) Not determinist order by with limit

[ https://issues.apache.org/jira/browse/PHOENIX-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882399#comment-15882399 ] chenglei edited comment on PHOENIX-3689 at 2/24/17 10:27 AM: - Thank your for

[jira] [Commented] (PHOENIX-3689) Not determinist order by with limit

[ https://issues.apache.org/jira/browse/PHOENIX-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882399#comment-15882399 ] chenglei commented on PHOENIX-3689: --- Thank your for adding DDL,but it seems that the sql given before

[jira] [Updated] (PHOENIX-3689) Not determinist order by with limit

[ https://issues.apache.org/jira/browse/PHOENIX-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur updated PHOENIX-3689: Description: The following request does not return the last value of myTable: select * from myTable order