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

ASF subversion and git services commented on IMPALA-10613:
----------------------------------------------------------

Commit 779d63b43f0978a36647bf6ace816a16ee19b2f7 in impala's branch 
refs/heads/master from Fang-Yu Rao
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=779d63b43 ]

IMPALA-15239: Remove the HMS server from Catalog server

This removes the implementation of HMS server within Catalog server due
to IMPALA-10613 and the related features added in the follow-up JIRA's,
since the HMS server within Catalog server is not actively used by the
community. This would also help us avoid issues like IMPALA-15110 and
IMPALA-15233 in the future when there are changes to Hive MetaStore.

Change-Id: I377a8ce0890055533ab7c78920ec17d6b47653b3
Assisted-by: Composer 2.5 (Cursor)
Reviewed-on: http://gerrit.cloudera.org:8080/24685
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> 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
>             Fix For: Impala 4.0.0
>
>
> 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.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to