[jira] [Commented] (PHOENIX-4395) Illegal data. Expected length of at least 49 bytes, but had 4 (state=22000,code=201)

[ https://issues.apache.org/jira/browse/PHOENIX-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260365#comment-16260365 ] Rajat Thakur commented on PHOENIX-4395: --- [~gjacoby] : I dint find any config property to turn off

[jira] [Commented] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2

[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260146#comment-16260146 ] James Taylor commented on PHOENIX-4372: --- Patch looks good to me, [~pboado]. Anyone else want to

[jira] [Comment Edited] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2

[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260101#comment-16260101 ] Pedro Boado edited comment on PHOENIX-4372 at 11/21/17 12:49 AM: - Sorry

[jira] [Updated] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2

[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Boado updated PHOENIX-4372: - Attachment: PHOENIX-4372-v4.patch Sorry about the whitespaces, I haven't noticed it. >

[jira] [Commented] (PHOENIX-4360) Prevent System.Catalog from splitting

[ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260085#comment-16260085 ] James Taylor commented on PHOENIX-4360: --- [~lhofhansl] - would you mind pushing this to

[jira] [Commented] (PHOENIX-4360) Prevent System.Catalog from splitting

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

[jira] [Commented] (PHOENIX-4360) Prevent System.Catalog from splitting

[ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259953#comment-16259953 ] Lars Hofhansl commented on PHOENIX-4360: Did 4.x-HBase-1.1 and 4.x-HBase-1.2. 4.x-HBase-0.98

[jira] [Commented] (PHOENIX-4360) Prevent System.Catalog from splitting

[ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259938#comment-16259938 ] Lars Hofhansl commented on PHOENIX-4360: Pushed to master. Doing other branches now. > Prevent

[jira] [Updated] (PHOENIX-4360) Prevent System.Catalog from splitting

[ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4360: --- Attachment: 4360-v2.txt -v2 has a test. I verified that the test fails without the updated

[jira] [Commented] (PHOENIX-4360) Prevent System.Catalog from splitting

[ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259650#comment-16259650 ] Lars Hofhansl commented on PHOENIX-4360: I'll add a test and then commit. Thanks for looking. >

[jira] [Commented] (PHOENIX-4395) Illegal data. Expected length of at least 49 bytes, but had 4 (state=22000,code=201)

[ https://issues.apache.org/jira/browse/PHOENIX-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259575#comment-16259575 ] Samarth Jain commented on PHOENIX-4395: --- [~gjacoby] - this error doesn't have to do with column

[jira] [Resolved] (PHOENIX-4394) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

[ https://issues.apache.org/jira/browse/PHOENIX-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-4394. - Resolution: Duplicate PHOENIX-4395 [~rajat.thakur], please be patient when you are creating

[jira] [Resolved] (PHOENIX-4391) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

[ https://issues.apache.org/jira/browse/PHOENIX-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-4391. - Resolution: Duplicate PHOENIX-4395 > ERROR 201 (22000): Illegal data. Expected length of at

[jira] [Resolved] (PHOENIX-4393) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

[ https://issues.apache.org/jira/browse/PHOENIX-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-4393. - Resolution: Duplicate PHOENIX-4395 > ERROR 201 (22000): Illegal data. Expected length of at

[jira] [Resolved] (PHOENIX-4392) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

[ https://issues.apache.org/jira/browse/PHOENIX-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-4392. - Resolution: Duplicate PHOENIX-4395 > ERROR 201 (22000): Illegal data. Expected length of at

[jira] [Resolved] (PHOENIX-4390) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

[ https://issues.apache.org/jira/browse/PHOENIX-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved PHOENIX-4390. - Resolution: Duplicate PHOENIX-4395 > ERROR 201 (22000): Illegal data. Expected length of at

[jira] [Commented] (PHOENIX-4395) Illegal data. Expected length of at least 49 bytes, but had 4 (state=22000,code=201)

[ https://issues.apache.org/jira/browse/PHOENIX-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259513#comment-16259513 ] Geoffrey Jacoby commented on PHOENIX-4395: -- I encountered the same issue recently. It turned

[jira] [Commented] (PHOENIX-4360) Prevent System.Catalog from splitting

[ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259487#comment-16259487 ] James Taylor commented on PHOENIX-4360: --- The other good reason for a test is to prevent an

[jira] [Commented] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2

[ https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259430#comment-16259430 ] James Taylor commented on PHOENIX-4372: --- Thanks for the patch, [~pboado]. Most of the files

Re: 4.13.0-HBase-1.1 not released?

Hi James, Sorry for the delay I wasn't on the dev mailing list, I'm interested to help and I can take the lead for the Hbase 1.1 release. Xavier On 2017-11-18 03:22 PM, James Taylor wrote: FYI, we'll do one final release for Phoenix on HBase 1.1 (look for a 4.13.1 release soon). It looks

[jira] [Commented] (PHOENIX-3176) Rows will be skipped which are having future timestamp in row_timestamp column

[ https://issues.apache.org/jira/browse/PHOENIX-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259394#comment-16259394 ] James Taylor commented on PHOENIX-3176: --- We use latest time stamp from the client now, so I

Re: 4.13.0-HBase-1.1 not released?

Hi Stepan, Please submit a patch on the JIRA. Thanks, James On Mon, Nov 20, 2017 at 1:38 AM Stepan Migunov < stepan.migu...@firstlinesoftware.com> wrote: > Good news, thank you. > > Btw, do you know if https://issues.apache.org/jira/browse/PHOENIX-4056 > still unresolved? That means that Phoenix

[jira] [Updated] (PHOENIX-3176) Rows will be skipped which are having future timestamp in row_timestamp column

[ https://issues.apache.org/jira/browse/PHOENIX-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3176: --- Fix Version/s: (was: 4.12.0) 4.14.0 > Rows will be skipped which are

[jira] [Reopened] (PHOENIX-3176) Rows will be skipped which are having future timestamp in row_timestamp column

[ https://issues.apache.org/jira/browse/PHOENIX-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal reopened PHOENIX-3176: > Rows will be skipped which are having future timestamp in row_timestamp column >

[jira] [Commented] (PHOENIX-3176) Rows will be skipped which are having future timestamp in row_timestamp column

[ https://issues.apache.org/jira/browse/PHOENIX-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259140#comment-16259140 ] Ankit Singhal commented on PHOENIX-3176: [~giacomotaylor], this doesn't seem to be fixed. Commit

[jira] [Updated] (PHOENIX-4395) Illegal data. Expected length of at least 49 bytes, but had 4 (state=22000,code=201)

[ https://issues.apache.org/jira/browse/PHOENIX-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajat Thakur updated PHOENIX-4395: -- Description: I am importing Oracle ExaData to Hbase via Sqoop. And query via phoenix . There

[jira] [Created] (PHOENIX-4395) Illegal data. Expected length of at least 49 bytes, but had 4 (state=22000,code=201)

Rajat Thakur created PHOENIX-4395: - Summary: Illegal data. Expected length of at least 49 bytes, but had 4 (state=22000,code=201) Key: PHOENIX-4395 URL: https://issues.apache.org/jira/browse/PHOENIX-4395

[jira] [Comment Edited] (PHOENIX-4374) Flakyness with Phoenix 4.13.0 and HBase 1.3.1: RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.NamespaceNotFoundExcep

[ https://issues.apache.org/jira/browse/PHOENIX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259114#comment-16259114 ] Francis Chuang edited comment on PHOENIX-4374 at 11/20/17 11:25 AM:

[jira] [Updated] (PHOENIX-4374) Flakyness with Phoenix 4.13.0 and HBase 1.3.1: RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.NamespaceNotFoundException:

[ https://issues.apache.org/jira/browse/PHOENIX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Chuang updated PHOENIX-4374: Attachment: hbase--master-m9edd51-phoenix.m9edd51-2017-11-20-second-run.log

[jira] [Commented] (PHOENIX-4374) Flakyness with Phoenix 4.13.0 and HBase 1.3.1: RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.NamespaceNotFoundException:

[ https://issues.apache.org/jira/browse/PHOENIX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259114#comment-16259114 ] Francis Chuang commented on PHOENIX-4374: - I was also able to get it to fail a second time, but

[jira] [Created] (PHOENIX-4394) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

Rajat Thakur created PHOENIX-4394: - Summary: ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4 Key: PHOENIX-4394 URL: https://issues.apache.org/jira/browse/PHOENIX-4394

[jira] [Updated] (PHOENIX-4374) Flakyness with Phoenix 4.13.0 and HBase 1.3.1: RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.NamespaceNotFoundException:

[ https://issues.apache.org/jira/browse/PHOENIX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Chuang updated PHOENIX-4374: Attachment: hbase--master-m9edd51-phoenix.m9edd51-2017-11-20.log

[jira] [Created] (PHOENIX-4391) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

Rajat Thakur created PHOENIX-4391: - Summary: ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4 Key: PHOENIX-4391 URL: https://issues.apache.org/jira/browse/PHOENIX-4391

[jira] [Created] (PHOENIX-4392) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

Rajat Thakur created PHOENIX-4392: - Summary: ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4 Key: PHOENIX-4392 URL: https://issues.apache.org/jira/browse/PHOENIX-4392

[jira] [Created] (PHOENIX-4393) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

Rajat Thakur created PHOENIX-4393: - Summary: ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4 Key: PHOENIX-4393 URL: https://issues.apache.org/jira/browse/PHOENIX-4393

[jira] [Created] (PHOENIX-4390) ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4

Rajat Thakur created PHOENIX-4390: - Summary: ERROR 201 (22000): Illegal data. Expected length of at least 49 bytes, but had 4 Key: PHOENIX-4390 URL: https://issues.apache.org/jira/browse/PHOENIX-4390

[jira] [Commented] (PHOENIX-4374) Flakyness with Phoenix 4.13.0 and HBase 1.3.1: RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.NamespaceNotFoundException:

[ https://issues.apache.org/jira/browse/PHOENIX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259106#comment-16259106 ] Francis Chuang commented on PHOENIX-4374: - I have reproduce the problem. This is the error

[jira] [Commented] (PHOENIX-4374) Flakyness with Phoenix 4.13.0 and HBase 1.3.1: RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.NamespaceNotFoundException:

[ https://issues.apache.org/jira/browse/PHOENIX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259055#comment-16259055 ] Francis Chuang commented on PHOENIX-4374: - I am currently planning to produce a dump of all the

Re: 4.13.0-HBase-1.1 not released?

Good news, thank you. Btw, do you know if https://issues.apache.org/jira/browse/PHOENIX-4056 still unresolved? That means that Phoenix is not compatible with spark 2.2. I see saveToPhoenix contains the follwing line: phxRDD.saveAsNewAPIHadoopFile("", ...). But spark 2.2 doesn't work if path

[jira] [Commented] (PHOENIX-4319) Zookeeper connection should be closed immediately

[ https://issues.apache.org/jira/browse/PHOENIX-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258942#comment-16258942 ] Prashant Agrawal commented on PHOENIX-4319: --- Actually we have CDH 4.9.2 running and we tried