Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
Description
Observed from the driver's log (June 16), when running the following custom SQL
select cast(row_key as integer) voter_id, cast(onecf['name'] as varchar(30)) name, cast(twocf['age'] as integer) age, cast(twocf['registration'] as varchar(20)) registration, cast(threecf['contributions'] as decimal(6,2)) contributions, cast(threecf['voterzone'] as integer) voterzone, cast(fourcf['create_date'] as timestamp) create_date from hbase.voter
Tableau will generate the following query
SELECT * FROM ( select cast(row_key as integer) voter_id,cast(onecf['name'] as varchar(30)) name,cast(twocf['age'] as integer) age, cast(twocf['registration'] as varchar(20)) registration, cast(threecf['contributions'] as decimal(6,2)) contributions, cast(threecf['voterzone'] as integer) voterzone,cast(fourcf['create_date'] as timestamp) create_date from hbase.voter ) `TableauSQL` WHERE (0 = 1)
In the case of HBase table resident in one region, it will return expected metadata.
But in the case of multi-region HBase table, it will return no metadata.
Updated:
Now, the above query will fail both for single-region and multi-region HBase table.
Attachments
Issue Links
- is related to
-
DRILL-884 Query used to derive result set metadata for Tableau's "Custom SQL" does not run
- Resolved