[IMPALA-728] HBase: NULL values not taken into account depending on the columns in SELECT

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: Impala 1.1.1
• Component/s: Backend
• Labels: impala
• Environment: IMPALA 1.1.1-1.p0.17; CDH 4.4.0-1.cdh4.4.0.p0.39
• Target Version: Product Backlog
• Assignee: Unassigned
• Reporter: Christophe S
• Created: 07/Jan/14 13:04
• Updated: 30/Oct/18 18:25
• Resolved: 30/Oct/18 18:25

Description

Data are in HBase:

CREATE EXTERNAL TABLE ttt (
id STRING,
...
...
...
)STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' WITH SERDEPROPERTIES ("hbase.columns.mapping" ="
:key,
...
...
...
") TBLPROPERTIES("hbase.table.name" = "TTTT");

select count from TTT where ColA = 'ABCDE'
==> 53 results

select * from TTT where ColA = 'ABCDE'
==> 178 results

select ColA from TTT where ColA = 'ABCDE'
==> 53 results

Looks like sometimes the 'NULL' values are taken into account and sometimes not.

Issue Links

• duplicates: IMPALA-283 select count(*) produces inconsistent results for hbase tables because of NULL projection
• is related to: IMPALA-6276 incorrect projection of null column in hbase
• relates to: IMPALA-283 select count(*) produces inconsistent results for hbase tables because of NULL projection