[
https://issues.apache.org/jira/browse/DRILL-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Meng updated DRILL-884:
----------------------------
Description:
The following style of query is used by Tableau to derive the metadata of a
custom SQL:
>From Tableau's protocol server log:
{code}
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocol::ReadMetadataImpl:
Attempting to read metadata from the prepared / executed query result set.
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
Reading metadata using a prepared statement.
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: <QUERY protocol='0367b1f0'>
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: SELECT *
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: FROM (
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: select * from
dfs.`default`.`/opt/drill/raw-files/click1.json`
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ) `TableauSQL`
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: WHERE (0 = 1)
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: </QUERY>
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
SQLPrepare failed. Reading metadata using an executed query.
2014-05-30 18:35:47.640 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl: No
columns were reported!
{code}
*Updated to avoid confusion:*
The above query is not the problem for the json file. It is because the query
fails for the json file.
{code}
SELECT `TableauSQL`.`address` AS `address`,
`TableauSQL`.`br` AS `br`,
`TableauSQL`.`first_visit` AS `first_visit`,
`TableauSQL`.`gender` AS `gender`,
`TableauSQL`.`id` AS `id`,
`TableauSQL`.`la` AS `la`,
`TableauSQL`.`name` AS `name`,
`TableauSQL`.`os` AS `os`,
`TableauSQL`.`st` AS `st`,
`TableauSQL`.`user_category` AS `user_category`
FROM (
select * from dfs.`default`.`/opt/drill/raw-files/click1.json`
) `TableauSQL`
{code}
However, there is a problem of Tableau generated metadata query in mult-region
HBase table (DRILL-1026).
was:
The following style of query is used by Tableau to derive the metadata of a
custom SQL:
>From Tableau's protocol server log:
{code}
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocol::ReadMetadataImpl:
Attempting to read metadata from the prepared / executed query result set.
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
Reading metadata using a prepared statement.
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: <QUERY protocol='0367b1f0'>
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: SELECT *
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: FROM (
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: select * from
dfs.`default`.`/opt/drill/raw-files/click1.json`
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ) `TableauSQL`
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: WHERE (0 = 1)
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: </QUERY>
2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
SQLPrepare failed. Reading metadata using an executed query.
2014-05-30 18:35:47.640 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl: No
columns were reported!
{code}
*Updated to avoid confusion:*
The above query is not the problem for the json file. It is because the query
fails for the json file.
{code}
SELECT `TableauSQL`.`address` AS `address`,
`TableauSQL`.`br` AS `br`,
`TableauSQL`.`first_visit` AS `first_visit`,
`TableauSQL`.`gender` AS `gender`,
`TableauSQL`.`id` AS `id`,
`TableauSQL`.`la` AS `la`,
`TableauSQL`.`name` AS `name`,
`TableauSQL`.`os` AS `os`,
`TableauSQL`.`st` AS `st`,
`TableauSQL`.`user_category` AS `user_category`
FROM (
select * from dfs.`default`.`/opt/drill/raw-files/click1.json`
) `TableauSQL`
{code}
However, there is a problem of Tableau generated metadata query in mult-region
HBase table (DRILL-1026).
> Query used to derive result set metadata for Tableau's "Custom SQL" does not
> run
> --------------------------------------------------------------------------------
>
> Key: DRILL-884
> URL: https://issues.apache.org/jira/browse/DRILL-884
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: George Chow
> Assignee: Steven Phillips
> Priority: Critical
> Labels: Tableau
> Fix For: 1.0.0-BETA1
>
> Attachments: DRILL-884.patch
>
>
> The following style of query is used by Tableau to derive the metadata of a
> custom SQL:
> From Tableau's protocol server log:
> {code}
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocol::ReadMetadataImpl:
> Attempting to read metadata from the prepared / executed query result set.
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
> Reading metadata using a prepared statement.
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: <QUERY protocol='0367b1f0'>
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: SELECT *
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: FROM (
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: select * from
> dfs.`default`.`/opt/drill/raw-files/click1.json`
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ) `TableauSQL`
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: WHERE (0 = 1)
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: </QUERY>
> 2014-05-30 18:35:39.718 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
> SQLPrepare failed. Reading metadata using an executed query.
> 2014-05-30 18:35:47.640 (-,-,-,-) 0ea0: ODBCProtocolImpl::ReadMetadataImpl:
> No columns were reported!
> {code}
> *Updated to avoid confusion:*
> The above query is not the problem for the json file. It is because the query
> fails for the json file.
> {code}
> SELECT `TableauSQL`.`address` AS `address`,
> `TableauSQL`.`br` AS `br`,
> `TableauSQL`.`first_visit` AS `first_visit`,
> `TableauSQL`.`gender` AS `gender`,
> `TableauSQL`.`id` AS `id`,
> `TableauSQL`.`la` AS `la`,
> `TableauSQL`.`name` AS `name`,
> `TableauSQL`.`os` AS `os`,
> `TableauSQL`.`st` AS `st`,
> `TableauSQL`.`user_category` AS `user_category`
> FROM (
> select * from dfs.`default`.`/opt/drill/raw-files/click1.json`
> ) `TableauSQL`
> {code}
> However, there is a problem of Tableau generated metadata query in
> mult-region HBase table (DRILL-1026).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
