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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Assignee: Manish Gupta
• Reporter: Manish Gupta
• Created: 11/Apr/17 11:36
• Updated: 14/Apr/17 07:29
• Resolved: 14/Apr/17 07:29

Description

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

Issue Links

• links to: GitHub Pull Request #781