You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Manish Gupta (JIRA)" <ji...@apache.org> on 2017/04/11 11:37:41 UTC

[jira] [Created] (CARBONDATA-900) Is null query on a newly added measure column is not returning proper results

Manish Gupta created CARBONDATA-900:
---------------------------------------

             Summary:  Is null query on a newly added measure column is not returning proper results
                 Key: CARBONDATA-900
                 URL: https://issues.apache.org/jira/browse/CARBONDATA-900
             Project: CarbonData
          Issue Type: Bug
            Reporter: Manish Gupta
            Assignee: Manish Gupta
            Priority: Minor
             Fix For: 1.1.0-incubating


When is null query is executed on newly added measure column, control goes to RowLevelFilterExecuterImpl class, where measure existence is checked. In case the measure is not found, bitset group is not getting populated with default values due to which that block is not returning any result.
Below queries can be executed to reproduce the issue:

CREATE TABLE uniqdata110 (CUST_ID int,CUST_NAME String) STORED BY 'carbondata'
LOAD DATA INPATH '<csvfilePath>' into table uniqdata110 OPTIONS('BAD_RECORDS_LOGGER_ENABLE'='TRUE', 'BAD_RECORDS_ACTION'='FORCE','FILEHEADER'='CUST_ID,CUST_NAME')
ALTER TABLE uniqdata110  ADD COLUMNS (a6 int)
LOAD DATA INPATH '<csvfilePath>' into table uniqdata110 OPTIONS('BAD_RECORDS_LOGGER_ENABLE'='TRUE', 'BAD_RECORDS_ACTION'='FORCE','FILEHEADER'='CUST_ID,CUST_NAME,a6')
select * from uniqdata110
select * from uniqdata110 where a6 is null

Data:
7,hello1
8,welcome1
bye,11




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)