[jira] [Commented] (PHOENIX-3523) Secondary index on case sensitive table breaks all queries

[ https://issues.apache.org/jira/browse/PHOENIX-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15747958#comment-15747958 ] Ankit Singhal commented on PHOENIX-3523: [~d.s.karthick], to create case sensitive table in the

[jira] [Commented] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753603#comment-15753603 ] Ankit Singhal commented on PHOENIX-3271: In this case, we are assuming that SELECT statement

[jira] [Assigned] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3271: -- Assignee: Ankit Singhal > Distribute UPSERT SELECT across cluster >

[jira] [Created] (PHOENIX-3540) Fix Time data type in Phoenix Spark integration

Ankit Singhal created PHOENIX-3540: -- Summary: Fix Time data type in Phoenix Spark integration Key: PHOENIX-3540 URL: https://issues.apache.org/jira/browse/PHOENIX-3540 Project: Phoenix

[jira] [Commented] (PHOENIX-3540) Fix Time data type in Phoenix Spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753632#comment-15753632 ] Ankit Singhal commented on PHOENIX-3540: [~jmahonin], can you please review it? > Fix Time data

[jira] [Updated] (PHOENIX-3539) Fix bulkload for StorageScheme - ONE_CELL_PER_KEYVALUE_COLUMN

[ https://issues.apache.org/jira/browse/PHOENIX-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3539: --- Attachment: PHOENIX-3539.patch > Fix bulkload for StorageScheme -

[jira] [Created] (PHOENIX-3539) Fix bulkload for StorageScheme - ONE_CELL_PER_KEYVALUE_COLUMN

Ankit Singhal created PHOENIX-3539: -- Summary: Fix bulkload for StorageScheme - ONE_CELL_PER_KEYVALUE_COLUMN Key: PHOENIX-3539 URL: https://issues.apache.org/jira/browse/PHOENIX-3539 Project:

[jira] [Updated] (PHOENIX-3540) Fix Time data type in Phoenix Spark integration

[ https://issues.apache.org/jira/browse/PHOENIX-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3540: --- Attachment: PHOENIX-3540.patch > Fix Time data type in Phoenix Spark integration >

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: PHOENIX-3271_v2.patch > Distribute UPSERT SELECT across cluster >

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

Ankit Singhal created PHOENIX-3583: -- Summary: Prepare IndexMaintainer on server itself Key: PHOENIX-3583 URL: https://issues.apache.org/jira/browse/PHOENIX-3583 Project: Phoenix Issue Type:

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

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

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: PHOENIX-3271_v2.patch Back on this today. Fixed the bugs with expressions

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: (was: PHOENIX-3271_v2.patch) > Distribute UPSERT SELECT across cluster >

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: PHOENIX-3271_v3.patch > Distribute UPSERT SELECT across cluster >

[jira] [Commented] (PHOENIX-2565) Store data for immutable tables in single KeyValue

[ https://issues.apache.org/jira/browse/PHOENIX-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784585#comment-15784585 ] Ankit Singhal commented on PHOENIX-2565: [~tdsilva], we had both fixed and variable width

[jira] [Commented] (PHOENIX-3460) Phoenix Spark plugin cannot find table with a Namespace prefix

[ https://issues.apache.org/jira/browse/PHOENIX-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15792656#comment-15792656 ] Ankit Singhal commented on PHOENIX-3460: Is the table name provided at the time of creation is

[jira] [Commented] (PHOENIX-3559) More disk space used with encoded column scheme with data in sparse columns

[ https://issues.apache.org/jira/browse/PHOENIX-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15797579#comment-15797579 ] Ankit Singhal commented on PHOENIX-3559: I did some comparison earlier with table having all

[jira] [Commented] (PHOENIX-3582) No significant space saving with immutable encoded column with large number of dense columns

[ https://issues.apache.org/jira/browse/PHOENIX-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814561#comment-15814561 ] Ankit Singhal commented on PHOENIX-3582: For test #1, It could be possible if varchar length is

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: (was: PHOENIX-3271_v3.patch) > Distribute UPSERT SELECT across cluster >

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814499#comment-15814499 ] Ankit Singhal commented on PHOENIX-3560: I think , if we set this to _1(greater than _0

[jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814497#comment-15814497 ] Ankit Singhal commented on PHOENIX-3560: I think , if we set this to _1(greater than _0

[jira] [Issue Comment Deleted] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns

[ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3560: --- Comment: was deleted (was: I think , if we set this to _1(greater than _0

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

[ https://issues.apache.org/jira/browse/PHOENIX-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3572: --- Assignee: Biju Nair > Support FETCH NEXT| n ROWS from Cursor >

[jira] [Assigned] (PHOENIX-3523) Secondary index on case sensitive table breaks all queries

[ https://issues.apache.org/jira/browse/PHOENIX-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-3523: -- Assignee: Ankit Singhal > Secondary index on case sensitive table breaks all queries

[jira] [Updated] (PHOENIX-3523) Secondary index on case sensitive table breaks all queries

[ https://issues.apache.org/jira/browse/PHOENIX-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3523: --- Attachment: PHOENIX-3523_wip.patch parking a wip patch here .. it fixes the above issue.

[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=15814812#comment-15814812 ] Ankit Singhal commented on PHOENIX-3572: I have already reviewed it offline, [~jamestaylor], do

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: PHOENIX-3271.patch [~jamestaylor], can you please review. > Distribute UPSERT

[jira] [Updated] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3271: --- Attachment: PHOENIX-3271_v1.patch > Distribute UPSERT SELECT across cluster >

[jira] [Commented] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

[ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782333#comment-15782333 ] Ankit Singhal commented on PHOENIX-3134: Added an option (--binaryEncoding or -b) to specify

[jira] [Commented] (PHOENIX-2565) Store data for immutable tables in single KeyValue

[ https://issues.apache.org/jira/browse/PHOENIX-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782480#comment-15782480 ] Ankit Singhal commented on PHOENIX-2565: [~tdsilva]/[~jamestaylor], are we considering any other

[jira] [Updated] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

[ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3134: --- Attachment: (was: PHOENIX-3134.patch) > varbinary fields bulk load difference between

[jira] [Updated] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

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

[jira] [Issue Comment Deleted] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

[ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3134: --- Comment: was deleted (was: [~sergey.soldatov], can you please review the attached patch.)

[jira] [Updated] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

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

[jira] [Comment Edited] (PHOENIX-2565) Store data for immutable tables in single KeyValue

[ https://issues.apache.org/jira/browse/PHOENIX-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782480#comment-15782480 ] Ankit Singhal edited comment on PHOENIX-2565 at 12/28/16 9:32 AM: --

[jira] [Commented] (PHOENIX-3548) Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.py

[ https://issues.apache.org/jira/browse/PHOENIX-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782346#comment-15782346 ] Ankit Singhal commented on PHOENIX-3548: option (--binaryEncoding or -b) to specify binary

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

Ankit Singhal created PHOENIX-3549: -- Summary: Fail if binary field in CSV is not properly base64 encoded Key: PHOENIX-3549 URL: https://issues.apache.org/jira/browse/PHOENIX-3549 Project: Phoenix

[jira] [Updated] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

[ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3134: --- Issue Type: Improvement (was: Bug) > varbinary fields bulk load difference between MR/psql

[jira] [Created] (PHOENIX-3548) Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.py

Ankit Singhal created PHOENIX-3548: -- Summary: Create documentation for binaryEncoding option for CSVBulkLoad/pSQL.py Key: PHOENIX-3548 URL: https://issues.apache.org/jira/browse/PHOENIX-3548

[jira] [Updated] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

[ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3134: --- Attachment: PHOENIX-3134_v1.patch > varbinary fields bulk load difference between MR/psql

[jira] [Commented] (PHOENIX-3160) Do index rebuilding with checkpointing (in round-robin fashion)

[ https://issues.apache.org/jira/browse/PHOENIX-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15777835#comment-15777835 ] Ankit Singhal commented on PHOENIX-3160: Automatic Index rebuild batch size can be controlled by

[jira] [Resolved] (PHOENIX-3160) Do index rebuilding with checkpointing (in round-robin fashion)

[ https://issues.apache.org/jira/browse/PHOENIX-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-3160. Resolution: Fixed Committed with PHOENIX-2890 > Do index rebuilding with checkpointing

[jira] [Created] (PHOENIX-3544) Fix UNSIGNED_DATE and UNSIGNED_TIME type in phoenix-spark

Ankit Singhal created PHOENIX-3544: -- Summary: Fix UNSIGNED_DATE and UNSIGNED_TIME type in phoenix-spark Key: PHOENIX-3544 URL: https://issues.apache.org/jira/browse/PHOENIX-3544 Project: Phoenix

[jira] [Commented] (PHOENIX-3271) Distribute UPSERT SELECT across cluster

[ https://issues.apache.org/jira/browse/PHOENIX-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764489#comment-15764489 ] Ankit Singhal commented on PHOENIX-3271: [~jamestaylor], sorry for the spam.. you can ignore

[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-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: --- Fix Version/s: 4.11.0 > spark 2.1 with Phoenix 4.10 load data as dataframe fail,

[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 fail,

[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 fail,

[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-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] [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=15955508#comment-15955508 ] Ankit Singhal commented on PHOENIX-3756: bq. The problem here was the case where the system

[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] [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. > Provide

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

[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. > Dropping

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

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

[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 names in

[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] [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] [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 normalization of

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

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

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

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

[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] [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 RS

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

[jira] [Comment Edited] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128594#comment-16128594 ] Ankit Singhal edited comment on PHOENIX-4083 at 8/16/17 10:14 AM: --

[jira] [Assigned] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reassigned PHOENIX-4083: -- Assignee: JC > Incorrect conditional when including OFFSET into explain plan >

[jira] [Resolved] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-4083. Resolution: Fixed Fix Version/s: 4.12.0 > Incorrect conditional when including

[jira] [Commented] (PHOENIX-4083) Incorrect conditional when including OFFSET into explain plan

[ https://issues.apache.org/jira/browse/PHOENIX-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128594#comment-16128594 ] Ankit Singhal commented on PHOENIX-4083: yes.. my bad. Thanks [~lifove] for pointing out. Just

[jira] [Comment Edited] (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=16086031#comment-16086031 ] Ankit Singhal edited comment on PHOENIX-4010 at 7/13/17 5:21 PM: -

[jira] [Comment Edited] (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=16086031#comment-16086031 ] Ankit Singhal edited comment on PHOENIX-4010 at 7/13/17 5:25 PM: -

[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=16083739#comment-16083739 ] Ankit Singhal commented on PHOENIX-4010: While implementing, I found that there is a problem in

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v1.patch Extended last patch with :- * Limit memory for hash join

[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=16086911#comment-16086911 ] Ankit Singhal commented on PHOENIX-4010: Thanks [~sergey.soldatov] and [~giacomotaylor] for the

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v2_rebased.patch > Hash Join cache may not be send to all

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010_v2.patch > Hash Join cache may not be send to all regionservers

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089582#comment-16089582 ] Ankit Singhal commented on PHOENIX-3163: It is getting reproduced with

[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=16089565#comment-16089565 ] Ankit Singhal commented on PHOENIX-4010: Thanks [~giacomotaylor] and [~sergey.soldatov] . I have

[jira] [Commented] (PHOENIX-4018) HashJoin may produce nulls for LHS table columns

[ https://issues.apache.org/jira/browse/PHOENIX-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089865#comment-16089865 ] Ankit Singhal commented on PHOENIX-4018: Yes, only last scanner should update the progress(which

[jira] [Comment Edited] (PHOENIX-4018) HashJoin may produce nulls for LHS table columns

[ https://issues.apache.org/jira/browse/PHOENIX-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089865#comment-16089865 ] Ankit Singhal edited comment on PHOENIX-4018 at 7/17/17 2:05 PM: - Yes,

[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=16082289#comment-16082289 ] Ankit Singhal commented on PHOENIX-4010: One option (discussed internally with [~devaraj] and

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010.patch > Hash Join cache may not be send to all regionservers when

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010.patch) > Hash Join cache may not be send to all

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010.patch > Hash Join cache may not be send to all regionservers when

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010.patch) > Hash Join cache may not be send to all

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

Ankit Singhal created PHOENIX-4010: -- Summary: Hash Join cache may not be send to all regionservers when we have stale HBase meta cache Key: PHOENIX-4010 URL: https://issues.apache.org/jira/browse/PHOENIX-4010

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: PHOENIX-4010.patch > Hash Join cache may not be send to all regionservers when

[jira] [Updated] (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:all-tabpanel ] Ankit Singhal updated PHOENIX-4010: --- Attachment: (was: PHOENIX-4010.patch) > Hash Join cache may not be send to all

[jira] [Comment Edited] (PHOENIX-3997) UngroupedAggregateRegionObserver.commitBatchWithHTable() should not check the memstore size and wait for flush.

[ https://issues.apache.org/jira/browse/PHOENIX-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077629#comment-16077629 ] Ankit Singhal edited comment on PHOENIX-3997 at 7/7/17 10:35 AM: - \+1

[jira] [Commented] (PHOENIX-3944) ReadOnlyTableException occurs when we map Phoenix view to an existing HBase table with Namespace Mapping enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077986#comment-16077986 ] Ankit Singhal commented on PHOENIX-3944: Thanks [~brfrn169] for the fix. Committed to master and

<    2   3   4   5   6   7   8   9   10   11   >