[ https://issues.apache.org/jira/browse/PHOENIX-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-2750: ---------------------------------- Fix Version/s: 4.8.0 > ERROR 201 (22000) when PERCENT_DISC over column(DOUBLE, BIGINT) that contain > null > --------------------------------------------------------------------------------- > > Key: PHOENIX-2750 > URL: https://issues.apache.org/jira/browse/PHOENIX-2750 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.5.1 > Environment: Phoenix 4.5.1 on hbase 1.1 > Reporter: Nick Hryhoriev > Fix For: 4.8.0 > > > I have a table > CREATE TABLE integration_tests.connector_test( > cf1.date_full timestamp, > cf1.date_empty timestamp, > cf1.date_with_null timestamp, > cf1.date_milliseconds bigint, > cf1.date_milliseconds_with_null bigint, > cf1.date_seconds bigint, > cf1.date_seconds_with_null bigint, > cf1.date_year bigint, > cf2.date_year_with_null bigint, > cf2.double_full DOUBLE, > cf2.double_with_null DOUBLE, > cf2.double_empty DOUBLE, > cf2.integer_full bigint, > cf3.integer_with_null bigint, > cf3.integer_empty bigint, > cf3.string_with_null varchar, > cf3.string_empty varchar, > cf3.string_full varchar, > id bigint, > CONSTRAINT pk PRIMARY KEY (id)) > SALT_BUCKETS=3, > DEFAULT_COLUMN_FAMILY='cf4', > COMPRESSION='GZ' > When i run PERCENT DISC query on column that contain null. > select ds.string_with_null, PERCENTILE_DISC(0.0) WITHIN GROUP (ORDER BY > ds.double_with_null ASC), PERCENTILE_DISC(0.25) WITHIN GROUP (ORDER BY > ds.double_with_null ASC), PERCENTILE_DISC(0.51) WITHIN GROUP (ORDER BY > ds.double_with_null ASC), PERCENTILE_DISC(1.0) WITHIN GROUP (ORDER BY > ds.double_with_null ASC) > from integration_tests.connector_test ds > where ds.date_full = (timestamp '2009-12-31 23:59:59.999') and ds.double_full > >= 300.0 > group by ds.string_with_null > i've got error > SQLException: ERROR 201 (22000): Illegal data. DOUBLE may not be null > when iterate through result set. > Is it expected behave? > how can i avoid it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)