Re: 答复: phoenix query server java.lang.ClassCastException for BIGINT ARRAY column

Definitely, someone who is maintaining CDH branch should take a look. I don't observer that behavior on the master branch: 0: jdbc:phoenix:thin:url=http://localhost:876> create table if not exists testarray(id bigint not null, events bigint array constraint pk primary key (id)); No rows affected

Re: hbase cell storage different bewteen bulk load and direct api

I believe we still rely on that empty key value, even for compact storage formats (though theoretically it could likely be made so we don't - JIRA, please?) A quick test would confirm: - upsert a row with no last_name or first_name - select * from T where last_name IS NULL If the row isn't

Re: hint to use a global index is not working - need to find out why

That looks strange. Could you please provide full DDLs for table and indexes? I just tried a similar scenario and obviously index is used: 0: jdbc:phoenix:> create table VARIANTJOIN_RTSALTED24 (id integer primary key, chrom_int integer, genomic_range integer); No rows affected (6.339 seconds) 0:

Re: hbase cell storage different bewteen bulk load and direct api

Heh. That looks like a bug actually. This is a 'dummy' KV ( https://phoenix.apache.org/faq.html#Why_empty_key_value), but I have some doubts that we need it for compacted rows. Thanks, Sergey On Thu, Apr 19, 2018 at 11:30 PM, Lew Jackman wrote: > I have not tried the

Re: pheonix client

This question is better asked on the Phoenix users list. The phoenix-client.jar is the one you need and is unique from the phoenix-core jar. Logging frameworks are likely not easily relocated/shaded to avoid issues which is why you're running into this. Can you provide the error you're

Re: hbase cell storage different bewteen bulk load and direct api

I have not tried the master yet branch yet, however on Phoenix 4.13 this storage discrepancy in hbase is still present with the extra column=M:\x00\x00\x00\x00 cells in hbase when using psql or sqlline. Does anyone have an understanding of the meaning of the column qualifier \x00\x00\x00\x00 ?

Re: hbase cell storage different bewteen bulk load and direct api

The upsert statement appears the same as the psql results - i.e. extra cells. I will try the master branch next. Thanks for the tip. -- Original Message -- From: Sergey Soldatov To: user@phoenix.apache.org Subject: Re: hbase cell storage different

hint to use a global index is not working - need to find out why

Hello Phoenix users, I am a novice Phoenix user and this is my first post to this user list. I did some searching in the list archives, but could not find an answer to what I hope is a simple question: my global index is being ignored, even after I add a Hint, and I want to know why. We are

答复: phoenix query server java.lang.ClassCastException for BIGINT ARRAY column

## Version: phoenix: 4.13.2-cdh5.11.2 hive: 1.1.0-cdh5.11.2 to reproduce: -- create table create table if not exists testarray(id bigint not null, events bigint array constraint pk primary key (id)) -- upsert data: upsert into testarray values (1, array[1,2]); -- query: select id from

答复: phoenix query server java.lang.ClassCastException for BIGINT ARRAY column

by the way, all the queries are shot in sqlline-thin.py 发件人: Lu Wei 发送时间: 2018年4月19日 6:51:15 收件人: user@phoenix.apache.org 主题: 答复: phoenix query server java.lang.ClassCastException for BIGINT ARRAY column ## Version: phoenix: 4.13.2-cdh5.11.2 hive:

Re: phoenix query server java.lang.ClassCastException for BIGINT ARRAY column

Could you please be more specific? Which version of phoenix are you using? Do you have a small script to reproduce? At first glance it looks like a PQS bug. Thanks, Sergey On Thu, Apr 19, 2018 at 8:17 AM, Lu Wei wrote: > Hi there, > > I have a phoenix table containing an

Re: hbase cell storage different bewteen bulk load and direct api

Hi Lew, no. 1st one looks line incorrect. You may file a bug on that ( I believe that the second case is correct, but you may also check with uploading data using regular upserts). Also, you may check whether the master branch has this issue. Thanks, Sergey On Thu, Apr 19, 2018 at 10:19 AM, Lew