Re: Phoenix Array Type Null Element

*An update on TIMESTAMP ARRAY test (for null elements):* CREATE TABLE TIMESTAMPARRAYTEST (ID VARCHAR, TS TIMESTAMP ARRAY CONSTRAINT PK PRIMARY KEY(ID)) Connection connection = getConnection(); Timestamp ts1 = new Timestamp(120550); Timestamp ts2 = new Timestamp(120750); Timestamp[] timeStampArray

Re: Phoenix Array Type Null Element

wouldn't converting to 0.0 instead of NULL create incorrect results in functions (like AVG, STDEV etc)? On Thu, May 7, 2015 at 11:14 AM, James Taylor wrote: > Agreed, we should make it uniform. See PHOENIX-777 - that'd be great > if Dumindu could work on that next. Take care to maintain backward

Re: Phoenix Array Type Null Element

Agreed, we should make it uniform. See PHOENIX-777 - that'd be great if Dumindu could work on that next. Take care to maintain backward compatibility in our array serialization format. Thanks, James On Thu, May 7, 2015 at 8:08 AM, Vasudevan, Ramkrishna S wrote: > James, > > > > It is not always

RE: Phoenix Array Type Null Element

James, It is not always true. For double we tend to convert the null to 0.0 instead of throwing exception. We should make the behavior uniform in this case. For varchar we support NULLs anyway explicitly. Regards Ram From: James Taylor [mailto:jamestay...@apache.org] Sent: Thursday, May 7, 2

Re: Phoenix Array Type Null Element

Note that for an array of primitive types (double, float, BIGINT, integer, smallint, tinyint), we don't support inserting null as an array element. On Thursday, May 7, 2015, Vasudevan, Ramkrishna S < ramkrishna.s.vasude...@intel.com> wrote: > Thanks for the detailed update, Kathir. > > > > *From

RE: Phoenix Array Type Null Element

Thanks for the detailed update, Kathir. From: Kathiresan S [mailto:kathiresanselva...@gmail.com] Sent: Thursday, May 7, 2015 7:50 PM To: user@phoenix.apache.org Subject: Re: Phoenix Array Type Null Element FYI - the version of code i used for bigint array and double array testing is (4.4.0-HBase

Re: Phoenix Array Type Null Element

FYI - the version of code i used for bigint array and double array testing is (4.4.0-HBase-0.98-rc0 + Patch from https://issues.apache.org/jira/browse/PHOENIX-1949 ). Now, the varchar array works fine after applying the patch. And regarding Double array null elements being returned as 0.0, is it i

RE: Phoenix Array Type Null Element

Thanks for the info. The NPE cases that was happening may get solved with the patch that I had attached. But for the BIGINT case we need to see the reason. Regards Ram From: Kathiresan S [mailto:kathiresanselva...@gmail.com] Sent: Thursday, May 7, 2015 7:24 PM To: user@phoenix.apache.org Subjec

Re: UDF - Access Tuple Column Values By Name

Thanks James. Thanks, Kathir On Wed, May 6, 2015 at 2:37 PM, James Taylor wrote: > +1 to Jaime's suggestion of providing multiple arguments. You can have > a variable number of arguments to a function by providing default > values for trailing arguments. I wouldn't rely on the Tuple argument >

Re: Phoenix Array Type Null Element

Yes Ram, i get below issues *BIGINT ARRAY* CREATE TABLE BIARRAYNULLTEST1 (ID VARCHAR, SALES BIGINT ARRAY CONSTRAINT PK PRIMARY KEY (ID)) Hbase>UPSERT INTO BIARRAYNULLTEST1 (ID, SALES) VALUES('123',ARRAY[1,2,null]) org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type mismatch.

Re: Re: CDH5.4.0 compatibility

What is the actual phoenix version that you want to get compatible with CDH 5.4.0 ？ Notice that CDH 5.4.0 integrates HBase 1.0 release internally and the git repo has already got phoenix 4.4.0-hbase-1.0-rc0 release that can be recompiled targeting at CDH 5.4.0 from here. Best, Sun. Cer

Re: CDH5.4.0 compatibility

Hi Srikanth, I really appreciate all you have done for the release, thank you so much ! 2015-05-07 14:14 GMT+08:00 Srikanth Srungarapu : > Hi, > Cloudera recently announced > > the inclusion of Apache Phoenix in labs. Pl