[jira] [Updated] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3797: --- Attachment: PHOENIX-3797_v2.patch > Local Index - Compaction fails on table with lo

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029614#comment-16029614 ] Ankit Singhal commented on PHOENIX-3797: [~jamestaylor], Yes Local Index data is in right sorted

[jira] [Commented] (PHOENIX-3881) Support Arrays in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029426#comment-16029426 ] Ankit Singhal commented on PHOENIX-3881: Current status(wip2 patch fixes ~165 test cases) {code

[jira] [Updated] (PHOENIX-3881) Support Arrays in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3881: --- Attachment: PHOENIX-3881_wip_2.patch > Support Arrays in phoenix-calc

[jira] [Comment Edited] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029290#comment-16029290 ] Ankit Singhal edited comment on PHOENIX-3797 at 5/30/17 1:05 PM: - Let's

[jira] [Updated] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3797: --- Attachment: PHOENIX-3797.patch > Local Index - Compaction fails on table with local in

[jira] [Commented] (PHOENIX-3797) Local Index - Compaction fails on table with local index due to non-increasing bloom keys

[ https://issues.apache.org/jira/browse/PHOENIX-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029290#comment-16029290 ] Ankit Singhal commented on PHOENIX-3797: Let's disable the repair scanner for now as it may take

[jira] [Resolved] (PHOENIX-3880) Is there any way to Move Phoenix table from one Hadoop Cluster to another (with Phoenix Metadata)

[ https://issues.apache.org/jira/browse/PHOENIX-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3880. Resolution: Invalid > Is there any way to Move Phoenix table from one Hadoop Clus

[jira] [Commented] (PHOENIX-3880) Is there any way to Move Phoenix table from one Hadoop Cluster to another (with Phoenix Metadata)

[ https://issues.apache.org/jira/browse/PHOENIX-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022794#comment-16022794 ] Ankit Singhal commented on PHOENIX-3880: Please reach out to u...@phoenix.apache.org

[jira] [Updated] (PHOENIX-3881) Support Arrays in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3881: --- Attachment: PHOENIX-3881_wip.patch > Support Arrays in phoenix-calc

[jira] [Updated] (PHOENIX-3882) Support Array functions

[ https://issues.apache.org/jira/browse/PHOENIX-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3882: --- Labels: calcite (was: ) > Support Array functi

[jira] [Created] (PHOENIX-3882) Support Array functions

Ankit Singhal created PHOENIX-3882: -- Summary: Support Array functions Key: PHOENIX-3882 URL: https://issues.apache.org/jira/browse/PHOENIX-3882 Project: Phoenix Issue Type: Sub-task

[jira] [Updated] (PHOENIX-3502) Support ARRAY DML in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3502: --- Issue Type: Sub-task (was: Improvement) Parent: PHOENIX-3881 > Support ARRAY

[jira] [Commented] (PHOENIX-3502) Support ARRAY DML in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022717#comment-16022717 ] Ankit Singhal commented on PHOENIX-3502: This is blocked on CALCITE-1804. > Support ARRAY

[jira] [Created] (PHOENIX-3881) Support Arrays in phoenix-calcite

Ankit Singhal created PHOENIX-3881: -- Summary: Support Arrays in phoenix-calcite Key: PHOENIX-3881 URL: https://issues.apache.org/jira/browse/PHOENIX-3881 Project: Phoenix Issue Type

[jira] [Assigned] (PHOENIX-3502) Support ARRAY DML in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3502: -- Assignee: Ankit Singhal > Support ARRAY DML in Calcite-Phoe

[jira] [Commented] (PHOENIX-3800) NPE when doing UPSERT SELECT into salted tables

[ https://issues.apache.org/jira/browse/PHOENIX-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997829#comment-15997829 ] Ankit Singhal commented on PHOENIX-3800: committed to master and 4.x branches. Sorry

[jira] [Assigned] (PHOENIX-3800) NPE when doing UPSERT SELECT into salted tables

[ https://issues.apache.org/jira/browse/PHOENIX-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3800: -- Assignee: Eiichi Sato > NPE when doing UPSERT SELECT into salted tab

[jira] [Commented] (PHOENIX-3800) NPE when doing UPSERT SELECT into salted tables

[ https://issues.apache.org/jira/browse/PHOENIX-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997820#comment-15997820 ] Ankit Singhal commented on PHOENIX-3800: +1, Thanks [~sato_eiichi] for the fix. Let me commit

[jira] [Resolved] (PHOENIX-3816) Implement SET_OPTION for consistency in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3816. Resolution: Fixed > Implement SET_OPTION for consistency in phoenix-calc

[jira] [Resolved] (PHOENIX-3809) CURRENT_DATE() (with parentheses) is illegal in Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3809. Resolution: Fixed > CURRENT_DATE() (with parentheses) is illegal in Calc

[jira] [Commented] (PHOENIX-3809) CURRENT_DATE() (with parentheses) is illegal in Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992461#comment-15992461 ] Ankit Singhal commented on PHOENIX-3809: Thanks [~julianhyde] and [~jamestaylor

[jira] [Updated] (PHOENIX-3816) Implement SET_OPTION for consistency in phoenix-calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3816: --- Summary: Implement SET_OPTION for consistency in phoenix-calcite (was: Implement

[jira] [Updated] (PHOENIX-3816) Implement SET_OPTION for consistency

[ https://issues.apache.org/jira/browse/PHOENIX-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3816: --- Attachment: PHOENIX-3816.patch -- patch that added the functionality to set ALTER SESSION

[jira] [Created] (PHOENIX-3816) Implement SET_OPTION for consistency

Ankit Singhal created PHOENIX-3816: -- Summary: Implement SET_OPTION for consistency Key: PHOENIX-3816 URL: https://issues.apache.org/jira/browse/PHOENIX-3816 Project: Phoenix Issue Type: Bug

[jira] [Resolved] (PHOENIX-3682) CURRENT_DATE and CURRENT_TIME cannot be resolved in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3682. Resolution: Duplicate Oops, missed this [~rajesh23], As discussion logged on PHOENIX-3809

[jira] [Assigned] (PHOENIX-3682) CURRENT_DATE and CURRENT_TIME cannot be resolved in Phoenix-Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3682: -- Assignee: (was: Rajeshbabu Chintaguntla) > CURRENT_DATE and CURRENT_TIME can

[jira] [Commented] (PHOENIX-3809) CURRENT_DATE() (with parentheses) is illegal in Calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988283#comment-15988283 ] Ankit Singhal commented on PHOENIX-3809: bq. I think having a version that allows parentheses

[jira] [Resolved] (PHOENIX-3814) Unable to connect to Phoenix via Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3814. Resolution: Duplicate > Unable to connect to Phoenix via Sp

[jira] [Commented] (PHOENIX-3814) Unable to connect to Phoenix via Spark

[ https://issues.apache.org/jira/browse/PHOENIX-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987205#comment-15987205 ] Ankit Singhal commented on PHOENIX-3814: Duplicate of PHOENIX-3721. you may try including hbase

[jira] [Commented] (PHOENIX-3710) Cannot use lowername data table name with indextool

[ https://issues.apache.org/jira/browse/PHOENIX-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982460#comment-15982460 ] Ankit Singhal commented on PHOENIX-3710: Thanks [~sergey.soldatov], changes look good

[jira] [Commented] (PHOENIX-3809) CURRENT_DATE() (with paranthesis) is illegal in calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981065#comment-15981065 ] Ankit Singhal commented on PHOENIX-3809: [~jamestaylor]/[~julianhyde], what can we do here

[jira] [Updated] (PHOENIX-3809) CURRENT_DATE() (with paranthesis) is illegal in calcite

[ https://issues.apache.org/jira/browse/PHOENIX-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3809: --- Description: Calcite doesn't allow system functions to be specified with parenthesis who

[jira] [Created] (PHOENIX-3809) CURRENT_DATE() (with paranthesis) is illegal in calcite

Ankit Singhal created PHOENIX-3809: -- Summary: CURRENT_DATE() (with paranthesis) is illegal in calcite Key: PHOENIX-3809 URL: https://issues.apache.org/jira/browse/PHOENIX-3809 Project: Phoenix

[jira] [Resolved] (PHOENIX-3751) spark 2.1 with Phoenix 4.10 load data as dataframe fail, NullPointerException

[ https://issues.apache.org/jira/browse/PHOENIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3751. Resolution: Fixed Thanks [~jmahonin], committed to master and 4.x branches. > spark

[jira] [Resolved] (PHOENIX-3792) Provide way to skip normalization of column names in phoenix-spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3792. Resolution: Fixed Thanks [~jmahonin], committed to master and 4.x branches. > Prov

[jira] [Resolved] (PHOENIX-3759) Dropping a local index causes NPE

[ https://issues.apache.org/jira/browse/PHOENIX-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3759. Resolution: Fixed Thanks [~lhofhansl], committed to master and 4.x branches. > Dropp

[jira] [Updated] (PHOENIX-3759) Dropping a local index causes NPE

[ https://issues.apache.org/jira/browse/PHOENIX-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3759: --- Fix Version/s: 4.11.0 > Dropping a local index causes

[jira] [Comment Edited] (PHOENIX-3792) Provide way to skip normalization of column names in phoenix-spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976709#comment-15976709 ] Ankit Singhal edited comment on PHOENIX-3792 at 4/20/17 1:48 PM: - Thanks

[jira] [Updated] (PHOENIX-3792) Provide way to skip normalization of column names in phoenix-spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3792: --- Attachment: PHOENIX-3792_v1.patch > Provide way to skip normalization of column na

[jira] [Commented] (PHOENIX-3792) Provide way to skip normalization of column names in phoenix-spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976709#comment-15976709 ] Ankit Singhal commented on PHOENIX-3792: Thanks [~jmahonin] for the review. Please find

[jira] [Comment Edited] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970391#comment-15970391 ] Ankit Singhal edited comment on PHOENIX-3360 at 4/16/17 1:40 PM: - bq

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970391#comment-15970391 ] Ankit Singhal commented on PHOENIX-3360: bq. Yes James Taylor we have observed index updates

[jira] [Comment Edited] (PHOENIX-3721) CSV bulk load doesn't work well with SYSTEM.MUTEX

[ https://issues.apache.org/jira/browse/PHOENIX-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970299#comment-15970299 ] Ankit Singhal edited comment on PHOENIX-3721 at 4/16/17 12:06 PM

[jira] [Updated] (PHOENIX-3792) Provide way to skip normalization of column names in phoenix-spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3792: --- Attachment: PHOENIX-3792.patch WDYT, [~jmahonin] > Provide way to skip normalizat

[jira] [Created] (PHOENIX-3792) Provide way to skip normalization of column names in phoenix-spark integration

Ankit Singhal created PHOENIX-3792: -- Summary: Provide way to skip normalization of column names in phoenix-spark integration Key: PHOENIX-3792 URL: https://issues.apache.org/jira/browse/PHOENIX-3792

[jira] [Commented] (PHOENIX-3721) CSV bulk load doesn't work well with SYSTEM.MUTEX

[ https://issues.apache.org/jira/browse/PHOENIX-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970299#comment-15970299 ] Ankit Singhal commented on PHOENIX-3721: [~sergey.soldatov], it looks similar to https

[jira] [Commented] (PHOENIX-3757) System mutex table not being created in SYSTEM namespace when namespace mapping is enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962521#comment-15962521 ] Ankit Singhal commented on PHOENIX-3757: bq. A little odd as we need to create this table after

[jira] [Updated] (PHOENIX-3759) Dropping a local index causes NPE

[ https://issues.apache.org/jira/browse/PHOENIX-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3759: --- Attachment: PHOENIX-3759.patch During major compaction when all the local indexes

[jira] [Commented] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956375#comment-15956375 ] Ankit Singhal commented on PHOENIX-3756: Thanks [~elserj] for the amendments, just one more fix

[jira] [Commented] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955508#comment-15955508 ] Ankit Singhal commented on PHOENIX-3756: bq. The problem here was the case where the system

[jira] [Comment Edited] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955446#comment-15955446 ] Ankit Singhal edited comment on PHOENIX-3756 at 4/4/17 5:16 PM: Thanks

[jira] [Commented] (PHOENIX-3756) Users lacking ADMIN on 'SYSTEM' HBase namespace can't connect to Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955446#comment-15955446 ] Ankit Singhal commented on PHOENIX-3756: Thanks [~elserj] for the update. * Can you also add

[jira] [Commented] (PHOENIX-3571) Potential divide by zero exception in LongDivideExpression

[ https://issues.apache.org/jira/browse/PHOENIX-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954961#comment-15954961 ] Ankit Singhal commented on PHOENIX-3571: [~tedyu], This is expected as per the test case. Do you

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954887#comment-15954887 ] Ankit Singhal commented on PHOENIX-3572: Thanks [~gsbiju], +1, Looks good to me. [~rajeshbabu

[jira] [Updated] (PHOENIX-3751) spark 2.1 with Phoenix 4.10 load data as dataframe fail, NullPointerException

[ https://issues.apache.org/jira/browse/PHOENIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3751: --- Attachment: PHOENIX-3751.patch > spark 2.1 with Phoenix 4.10 load data as dataframe f

[jira] [Updated] (PHOENIX-3751) spark 2.1 with Phoenix 4.10 load data as dataframe fail, NullPointerException

[ https://issues.apache.org/jira/browse/PHOENIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3751: --- Fix Version/s: 4.11.0 > spark 2.1 with Phoenix 4.10 load data as dataframe f

[jira] [Commented] (PHOENIX-3751) spark 2.1 with Phoenix 4.10 load data as dataframe fail, NullPointerException

[ https://issues.apache.org/jira/browse/PHOENIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954854#comment-15954854 ] Ankit Singhal commented on PHOENIX-3751: Thanks [~angelfox] for reporting it with details

[jira] [Assigned] (PHOENIX-3751) spark 2.1 with Phoenix 4.10 load data as dataframe fail, NullPointerException

[ https://issues.apache.org/jira/browse/PHOENIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3751: -- Assignee: Ankit Singhal > spark 2.1 with Phoenix 4.10 load data as dataframe f

Re: [VOTE] Release of Apache Phoenix 4.10.0 RC0

PHOENIX-3726 could be a blocker for this release. On Wed, Mar 8, 2017 at 3:40 AM, James Taylor wrote: > Hello Everyone, > > This is a call for a vote on Apache Phoenix 4.10.0 RC0. This is the next > minor release of Phoenix 4, compatible with Apache HBase 0.98, 1.1 &

[jira] [Updated] (PHOENIX-3726) Error while upgrading system tables

[ https://issues.apache.org/jira/browse/PHOENIX-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3726: --- Fix Version/s: 4.10.0 > Error while upgrading system tab

[jira] [Updated] (PHOENIX-3726) Error while upgrading system tables

[ https://issues.apache.org/jira/browse/PHOENIX-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3726: --- Priority: Blocker (was: Major) > Error while upgrading system tab

[jira] [Updated] (PHOENIX-3649) 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 ] Ankit Singhal updated PHOENIX-3649: --- Attachment: PHOENIX-3649_4.9_branch.patch > higher memory consumption on RS leading to

[jira] [Updated] (PHOENIX-3649) 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 ] Ankit Singhal updated PHOENIX-3649: --- Summary: higher memory consumption on RS leading to OOM/abort on immutable index creation

[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 ] Ankit Singhal updated PHOENIX-3649: --- Attachment: PHOENIX-3649_v3.patch > After PHOENIX-3271 higher memory consumption on

[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=15896765#comment-15896765 ] Ankit Singhal commented on PHOENIX-3649: bq. The only problem is that the index will be active

[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=15892131#comment-15892131 ] Ankit Singhal commented on PHOENIX-3649: Thanks [~giacomotaylor] for explaining it in detail

[jira] [Commented] (PHOENIX-3583) Prepare IndexMaintainer on server itself

[ https://issues.apache.org/jira/browse/PHOENIX-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889845#comment-15889845 ] Ankit Singhal commented on PHOENIX-3583: bq. We have logic on the client-side in MutationState

[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=15889837#comment-15889837 ] Ankit Singhal commented on PHOENIX-3649: bq. Does PHOENIX-3271 set the time stamp

[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 ] Ankit Singhal updated PHOENIX-3649: --- Attachment: PHOENIX-3649_v1.patch v1 patch for test execution. [~giacomotaylor

[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_v1.patch > Drop schema does not invalidate schema from the ser

[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=15885634#comment-15885634 ] Ankit Singhal commented on PHOENIX-3694: Thanks [~sergey.soldatov], committed v1 in 4.x-HBase

[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 ser

[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] [Updated] (PHOENIX-3688) Rebuild(ALTER INDEX IDX ON TABLE REBUILD) of indexes created on table having row_timestamp column will result in no data visible to the User for that Index.

[ https://issues.apache.org/jira/browse/PHOENIX-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3688: --- Reporter: Cheng Xu (was: Ankit Singhal) > Rebuild(ALTER INDEX IDX ON TABLE REBU

[jira] [Commented] (PHOENIX-3572) Support FETCH NEXT| n ROWS from Cursor

[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863302#comment-15863302 ] Ankit Singhal commented on PHOENIX-3572: [~gsbiju], requires some cleanup so have left some

[jira] [Updated] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3652: --- Attachment: PHOENIX-3652_addendum3.patch how about addendum3 [~elserj]? using a deprecated

[jira] [Commented] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854324#comment-15854324 ] Ankit Singhal commented on PHOENIX-3652: sorry [~elserj], addendum2 is also wrong because we

[jira] [Updated] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3652: --- Attachment: PHOENIX-3652_addendum2.patch > Users who do not have global access to hb

[jira] [Commented] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854316#comment-15854316 ] Ankit Singhal commented on PHOENIX-3652: Thanks [~elserj], but actual patch is to avoid getting

[jira] [Updated] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3652: --- Attachment: (was: PHOENIX-3652_4.8.patch) > Users who do not have global acc

[jira] [Updated] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3652: --- Attachment: PHOENIX-3652_4.8.patch > Users who do not have global access to hbase clus

[jira] [Resolved] (PHOENIX-3652) Users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3652. Resolution: Fixed Thanks [~sergey.soldatov] for the review. committed to 4.8, 4.x

[jira] [Commented] (PHOENIX-3214) Kafka Phoenix Consumer

[ https://issues.apache.org/jira/browse/PHOENIX-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854135#comment-15854135 ] Ankit Singhal commented on PHOENIX-3214: ping [~jmahonin], it seems it broke 4.x-HBase-0.98

[jira] [Resolved] (PHOENIX-3610) Fix tableName used to get the index maintainers while creating HalfStoreFileReader for local index store

[ https://issues.apache.org/jira/browse/PHOENIX-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3610. Resolution: Fixed Thanks [~rajeshbabu], committed to master and 4.x branches. >

[jira] [Updated] (PHOENIX-3610) Fix tableName used to get the index maintainers while creating HalfStoreFileReader for local index store

[ https://issues.apache.org/jira/browse/PHOENIX-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3610: --- Attachment: PHOENIX-3610_v1.patch [~rajeshbabu], can you please review the attached patch

[jira] [Commented] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853641#comment-15853641 ] Ankit Singhal commented on PHOENIX-3609: Thanks [~rajeshbabu] for the review. committed

[jira] [Commented] (PHOENIX-3495) Ignore NamespaceExistException when namespace mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853622#comment-15853622 ] Ankit Singhal commented on PHOENIX-3495: [~samarthjain], I think the patch requires Global(Admin

[jira] [Updated] (PHOENIX-3652) users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3652: --- Fix Version/s: 4.8.3 4.10.0 > users who do not have global acc

[jira] [Updated] (PHOENIX-3652) users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3652: --- Attachment: PHOENIX-3652.patch PHOENIX-3652_4.8.patch > users who

[jira] [Commented] (PHOENIX-3652) users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853612#comment-15853612 ] Ankit Singhal commented on PHOENIX-3652: [~sergey.soldatov], can you please review the attached

[jira] [Assigned] (PHOENIX-3652) users who do not have global access to hbase cluster can't connect to phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3652: -- Assignee: Ankit Singhal > users who do not have global access to hbase cluster ca

[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 ] Ankit Singhal updated PHOENIX-3649: --- Attachment: PHOENIX-3649.patch > After PHOENIX-3271 higher memory consumption on RS lead

[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=15851331#comment-15851331 ] Ankit Singhal commented on PHOENIX-3649: It is actually after PHOENIX-3396(https://github.com

[jira] [Updated] (PHOENIX-3610) Fix tableName used to get the index maintainers while creating HalfStoreFileReader for local index store

[ https://issues.apache.org/jira/browse/PHOENIX-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3610: --- Attachment: PHOENIX-3610.patch > Fix tableName used to get the index maintainers wh

[jira] [Commented] (PHOENIX-3583) Prepare IndexMaintainer on server itself

[ https://issues.apache.org/jira/browse/PHOENIX-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832175#comment-15832175 ] Ankit Singhal commented on PHOENIX-3583: bq. I don't think we need to prepare it on the server

[jira] [Updated] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3609: --- Attachment: (was: PHOENIX-3609_v1.patch) > Detect and fix corrupted local index reg

[jira] [Updated] (PHOENIX-3609) Detect and fix corrupted local index region during compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3609: --- Attachment: PHOENIX-3609_v1.patch > Detect and fix corrupted local index region dur

[jira] [Commented] (PHOENIX-3608) KeyRange interset should return EMPTY_RANGE when one of it is NULL_RANGE

[ https://issues.apache.org/jira/browse/PHOENIX-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831290#comment-15831290 ] Ankit Singhal commented on PHOENIX-3608: Good find [~chrajeshbab...@gmail.com], +1 > KeyRa

[jira] [Updated] (PHOENIX-3549) Fail if binary field in CSV is not properly base64 encoded

[ https://issues.apache.org/jira/browse/PHOENIX-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3549: --- Fix Version/s: 4.10.0 > Fail if binary field in CSV is not properly base64 enco

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