[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-3538) Regex Bulkload Tool

[ https://issues.apache.org/jira/browse/PHOENIX-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814199#comment-15814199 ] Gabriel Reid commented on PHOENIX-3538: --- Thanks for the update [~kalyanhadoop]. However, the

[jira] [Comment Edited] (PHOENIX-3555) Building async local index by IndexTool generate wrong data

[ https://issues.apache.org/jira/browse/PHOENIX-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814184#comment-15814184 ] chenzhiming edited comment on PHOENIX-3555 at 1/10/17 7:30 AM: --- Sorry

[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] [Commented] (PHOENIX-3555) Building async local index by IndexTool generate wrong data

[ https://issues.apache.org/jira/browse/PHOENIX-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814184#comment-15814184 ] chenzhiming commented on PHOENIX-3555: -- Sorry about that,the bad network lead to repeat

[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-3554) Building async local index by IndexTool generate wrong data

[ https://issues.apache.org/jira/browse/PHOENIX-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenzhiming updated PHOENIX-3554: - Description: 1.a salt table which pk is varchar CREATE TABLE C_PICRECORD ( ID VARCHAR NOT

[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] [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_v2.patch Back on this today. Fixed the bugs with expressions

[jira] [Commented] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814117#comment-15814117 ] Rajeshbabu Chintaguntla commented on PHOENIX-3579: -- There are many tests failing with

[jira] [Updated] (PHOENIX-3567) Use argparse in sqlline.py

[ https://issues.apache.org/jira/browse/PHOENIX-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-3567: Attachment: PHOENIX-3567.003.patch .003 Just removes the user and password options to sqlline as

[jira] [Updated] (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:all-tabpanel ] Mujtaba Chohan updated PHOENIX-3582: Assignee: Samarth Jain > No significant space saving with immutable encoded column with

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

Mujtaba Chohan created PHOENIX-3582: --- Summary: No significant space saving with immutable encoded column with large number of dense columns Key: PHOENIX-3582 URL:

[jira] [Updated] (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 ] Mujtaba Chohan updated PHOENIX-3560: Attachment: DataGenerator.java Synthetic data generator attached. > Aggregate query

[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=15813531#comment-15813531 ] Mujtaba Chohan commented on PHOENIX-3560: - [~samarthjain] Patch didn't make much difference.

[jira] [Assigned] (PHOENIX-3447) Add upgrade code to add the required metadata columns for supporting column encoding

[ https://issues.apache.org/jira/browse/PHOENIX-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reassigned PHOENIX-3447: - Assignee: Samarth Jain > Add upgrade code to add the required metadata columns for

[jira] [Assigned] (PHOENIX-3443) Support different encoding schemes (BYTE, SHORT, INTEGER) for storing encoded column qualifiers

[ https://issues.apache.org/jira/browse/PHOENIX-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reassigned PHOENIX-3443: - Assignee: Samarth Jain > Support different encoding schemes (BYTE, SHORT, INTEGER) for

[jira] [Updated] (PHOENIX-3447) Add upgrade code to add the required metadata columns for supporting column encoding

[ https://issues.apache.org/jira/browse/PHOENIX-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3447: -- Attachment: PHOENIX-3447.patch [~jamestaylor], would you mind taking a look. I had to write a

[jira] [Commented] (PHOENIX-3457) Adjust build settings in pom to improve consistency

[ https://issues.apache.org/jira/browse/PHOENIX-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813385#comment-15813385 ] Josh Elser commented on PHOENIX-3457: - Looks like this should be closed, [~jamestaylor]? > Adjust

[jira] [Resolved] (PHOENIX-3552) JDBC connectivity is very slow with Phoenix Client driver

[ https://issues.apache.org/jira/browse/PHOENIX-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-3552. - Resolution: Invalid This is not a valid JIRA issue. Use the us...@phoenix.apache.org mailing

[jira] [Resolved] (PHOENIX-3580) Phoenix user rights issues

[ https://issues.apache.org/jira/browse/PHOENIX-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-3580. - Resolution: Invalid Fix Version/s: (was: 4.8.2) This is not a valid issue to paste

[jira] [Resolved] (PHOENIX-3555) Building async local index by IndexTool generate wrong data

[ https://issues.apache.org/jira/browse/PHOENIX-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-3555. - Resolution: Duplicate Duplicate of PHOENIX-3554 > Building async local index by IndexTool

[jira] [Commented] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813340#comment-15813340 ] ChiaPing Tsai commented on PHOENIX-3569: bq. Moving the index updates to postPut/postDelete will

Optimisation for times series

Hi Phoenix, I use Phoenix for 1 year and HBase since 2 years. and I really think phoenix leverage Hbase.. But I'm still surprised that the column oriented storage isn't totally used. The dynamic column feature allow you to upsert or select a column not created in the create table statement,

[jira] [Commented] (PHOENIX-3538) Regex Bulkload Tool

[ https://issues.apache.org/jira/browse/PHOENIX-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812736#comment-15812736 ] Gabriel Reid commented on PHOENIX-3538: --- Sorry for such a slow reply on this [~kalyanhadoop].

[jira] [Updated] (PHOENIX-3581) Class-cast exceptions caused by TestUtil.getSplits() and TestUtil.getGuidePostsList()

[ https://issues.apache.org/jira/browse/PHOENIX-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated PHOENIX-3581: - Issue Type: Sub-task (was: Bug) Parent: PHOENIX-3104 > Class-cast exceptions caused by

[jira] [Created] (PHOENIX-3581) Class-cast exceptions caused by TestUtil.getSplits() and TestUtil.getGuidePostsList()

Maryann Xue created PHOENIX-3581: Summary: Class-cast exceptions caused by TestUtil.getSplits() and TestUtil.getGuidePostsList() Key: PHOENIX-3581 URL: https://issues.apache.org/jira/browse/PHOENIX-3581

[jira] [Commented] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812504#comment-15812504 ] Maryann Xue commented on PHOENIX-3579: -- Thank you very much for the initial patch, [~kliew]! But I

[jira] [Resolved] (PHOENIX-3357) Issue with column re-ordering in column family support for Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-3357. -- Resolution: Fixed This has been fixed by CALCITE-1425 > Issue with column re-ordering in

[jira] [Updated] (PHOENIX-3580) Phoenix user rights issues

[ https://issues.apache.org/jira/browse/PHOENIX-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuwanru updated PHOENIX-3580: - Description: I have modified the ‘phoenix.schema.isNamespaceMappingEnabled’ property to true,restart

[jira] [Commented] (PHOENIX-3351) Implement TODOs in PhoenixTableModify#upsert to allow writes to tenant specific tables

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

[jira] [Created] (PHOENIX-3580) Phoenix user rights issues

wuwanru created PHOENIX-3580: Summary: Phoenix user rights issues Key: PHOENIX-3580 URL: https://issues.apache.org/jira/browse/PHOENIX-3580 Project: Phoenix Issue Type: Bug Affects Versions:

[jira] [Commented] (PHOENIX-3569) Deadlock when updating both of local and global index

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

[jira] [Updated] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ChiaPing Tsai updated PHOENIX-3569: --- Attachment: PHOENIX-3569.fail.patch The fail.patch contains the unit test only. We can run

[jira] [Commented] (PHOENIX-3569) Deadlock when updating both of local and global index

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

[jira] [Commented] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811543#comment-15811543 ] ChiaPing Tsai commented on PHOENIX-3569: i have attached the log file. > Deadlock when updating

[jira] [Updated] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ChiaPing Tsai updated PHOENIX-3569: --- Attachment: hbase-root-regionserver-node04.ncku.edu.tw.log > Deadlock when updating both of

Re: Renaming Phoenix table

Thanks James! I would try that when I have some spare cycles - Youngwoo On Fri, Jan 6, 2017 at 4:00 AM, James Taylor wrote: > Hi Youngwoo, > > Correct - no support for renaming a table in Phoenix currently > (see PHOENIX-2341). Apparently, you can use the HBase

Re: Dropping local index on large table caused crash of region servers

Thank you guys. Good to know that. Samarth, Following is the output from CLI: > drop index TBL_IDX1 ON MYSCHEMA.TBL; Error: Operation timed out. (state=TIM01,code=6000) java.sql.SQLTimeoutException: Operation timed out. at

[jira] [Comment Edited] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811485#comment-15811485 ] Rajeshbabu Chintaguntla edited comment on PHOENIX-3569 at 1/9/17 11:07 AM:

[jira] [Comment Edited] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811485#comment-15811485 ] Rajeshbabu Chintaguntla edited comment on PHOENIX-3569 at 1/9/17 11:06 AM:

[jira] [Commented] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811485#comment-15811485 ] Rajeshbabu Chintaguntla commented on PHOENIX-3569: -- [~chia7712] Moving the index

[jira] [Commented] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811460#comment-15811460 ] Rajeshbabu Chintaguntla commented on PHOENIX-3579: -- [~kliew] FYI as part of

[jira] [Updated] (PHOENIX-3351) Implement TODOs in PhoenixTableModify#upsert to allow writes to tenant specific tables

[ https://issues.apache.org/jira/browse/PHOENIX-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3351: - Attachment: PHOENIX-3351_master.patch Here is the master branch code

[jira] [Updated] (PHOENIX-3351) Implement TODOs in PhoenixTableModify#upsert to allow writes to tenant specific tables

[ https://issues.apache.org/jira/browse/PHOENIX-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3351: - Attachment: PHOENIX-3351.patch [~giacomotaylor] [~maryannxue] It's the

[jira] [Updated] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ChiaPing Tsai updated PHOENIX-3569: --- Attachment: PHOENIX-3569.v1.patch v1 fixes the QA errors > Deadlock when updating both of

[jira] [Updated] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Liew updated PHOENIX-3579: Attachment: PHOENIX-3579.2.patch > INSERT/UPSERT should allow values less than number of columns

[jira] [Commented] (PHOENIX-3569) Deadlock when updating both of local and global index

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

[jira] [Comment Edited] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811152#comment-15811152 ] Kevin Liew edited comment on PHOENIX-3579 at 1/9/17 9:29 AM: - Preliminary

[jira] [Updated] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Liew updated PHOENIX-3579: Attachment: PHOENIX-3579.patch Preliminary patch attached. Some test cases fail due to column

[jira] [Created] (PHOENIX-3579) INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix

Kevin Liew created PHOENIX-3579: --- Summary: INSERT/UPSERT should allow values less than number of columns in Calcite-Phoenix Key: PHOENIX-3579 URL: https://issues.apache.org/jira/browse/PHOENIX-3579

[jira] [Updated] (PHOENIX-3569) Deadlock when updating both of local and global index

[ https://issues.apache.org/jira/browse/PHOENIX-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ChiaPing Tsai updated PHOENIX-3569: --- Attachment: PHOENIX-3569.v0.patch v0 has two changes. # the local index updates is called