[
https://issues.apache.org/jira/browse/IMPALA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351551#comment-17351551
]
ASF subversion and git services commented on IMPALA-10613:
----------------------------------------------------------
Commit 8087c75f62504f177b0a1c9f02eecc4eb81e00fc in impala's branch
refs/heads/master from Vihang Karajgaonkar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=8087c75 ]
IMPALA-10613: (addendum) Fix test on S3 builds
The test_metastore_service.py fails on S3 builds because it expects
the filemetadata's object dictionary to be present. However, if the
table is located on S3 then there are no file-blocks in the returned
file-metadata and hence the length of obj_dict will be 0.
This patch fixes the test in S3 builds by not asserting the check
on S3, ADLS, GCS builds.
Testing Done:
1. Ran the test locally to confirm it is working.
2. [WIP] Ran the test on a S3 environment where tables are created
on S3.
Change-Id: I6ac291529dc0661abdfc2d4f48924a2c4b807c40
Reviewed-on: http://gerrit.cloudera.org:8080/17483
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Vihang Karajgaonkar <[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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
