[
https://issues.apache.org/jira/browse/IMPALA-13947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086848#comment-18086848
]
ASF subversion and git services commented on IMPALA-13947:
----------------------------------------------------------
Commit 9b0f0686136d8d79af03687898fe3205f81a6700 in impala's branch
refs/heads/master from Noemi Pap-Takacs
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=9b0f06861 ]
IMPALA-14857: [DOCS] Update metadata management documentation
Since IMPALA-13947 the default catalog mode changed from legacy
to local catalog mode. This change updates the docs and includes
the necessary startup flags to return to legacy catalog mode.
Testing: built docs
Change-Id: Id3a28be159420d33bafe43dfec2099a388451e03
Generated-by: GPT-5.3.-Codex
Reviewed-on: http://gerrit.cloudera.org:8080/24150
Reviewed-by: Quanlong Huang <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Turn on local-catalog mode by default
> -------------------------------------
>
> Key: IMPALA-13947
> URL: https://issues.apache.org/jira/browse/IMPALA-13947
> Project: IMPALA
> Issue Type: Task
> Components: Catalog
> Reporter: Quanlong Huang
> Assignee: Riza Suminto
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> This aims to turn on local-catalog mode by default.
> One behavior change is FileSystem permission checks will be defered to the
> execution stage (IMPALA-7539). Note that in the legacy catalog mode,
> permission checks are done in planning stage so illegal queries can fail
> before execution. But preloading all the dir/file permissions is found to be
> a bottleneck of metadata loading on large tables. So we decided to skip it in
> IMPALA-12929.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
