[
https://issues.apache.org/jira/browse/HIVE-27583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihua Deng updated HIVE-27583:
-------------------------------
Description: Following the discussion on HIVE-27487, in general the JDBC
storage handler adds limit 1 to the query in order to fetch the metadata, say
the column names and its types. This jira is trying to explore if we can add
"limit 0" to the query as we don't care about the records returned, and confirm
that the predicate is pushed down to the storage, this will reduce the overhead
of executing the query. (was: Following the discussion on HIVE-27487, In
general the JDBC storage handler adds limit 1 to the query in order to fetch
the metadata, say the column names and its types. This jira is trying to
explore if we can add "limit 0" to the query as we don't care about the records
returned, and confirm that the predicate is pushed down to the storage, this
will reduce the overhead of executing the query.)
> Get the meta of query with limit 0 in JDBC storage handler
> ----------------------------------------------------------
>
> Key: HIVE-27583
> URL: https://issues.apache.org/jira/browse/HIVE-27583
> Project: Hive
> Issue Type: Improvement
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
>
> Following the discussion on HIVE-27487, in general the JDBC storage handler
> adds limit 1 to the query in order to fetch the metadata, say the column
> names and its types. This jira is trying to explore if we can add "limit 0"
> to the query as we don't care about the records returned, and confirm that
> the predicate is pushed down to the storage, this will reduce the overhead of
> executing the query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
