[ 
https://issues.apache.org/jira/browse/IMPALA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311856#comment-17311856
 ] 

Vihang Karajgaonkar commented on IMPALA-10613:
----------------------------------------------

https://gerrit.cloudera.org/#/c/17244/ for the review

> Expose table and partition metadata over HMS API
> ------------------------------------------------
>
>                 Key: IMPALA-10613
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10613
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Major
>
> Catalogd caches the table and partition metadata. If an external FE needs to 
> be supported to query using the Impala, it would need to get this metadata 
> from catalogd to compile the query and generate the plan. While a subset of 
> the metadata which is cached in catalogd, is sourced from Hive metastore, it 
> also caches file metadata which is needed by the Impala backend to create the 
> Impala plan. It would be good to expose the table and partition metadata 
> cached in catalogd over HMS API so that any Hive metastore client (e.g spark, 
> hive) can potentially use this metadata to create a plan. This JIRA tracks 
> the work needed to expose this information over catalogd.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to