[
https://issues.apache.org/jira/browse/IMPALA-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057606#comment-18057606
]
ASF subversion and git services commented on IMPALA-14341:
----------------------------------------------------------
Commit cd82ac735d06f85665043558ff90007df082c0c3 in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=cd82ac735 ]
IMPALA-14341: Iceberg MetaProviders Blacklist DBs/Tables
Databases and tables managed by Iceberg Rest Catalogs are
now filtered based on the blacklisted dbs and tables
startup parameters.
Testing was accomplished by new JUnit tests to exercise
Java code and custom cluster tests that run queries against
blacklisted dbs and tables.
Generated-by: Github Copilot (Claude Sonnet 4.5)
Change-Id: I73a06d30dcdbb579f92c2afa5928beb6c5a13348
Reviewed-on: http://gerrit.cloudera.org:8080/23833
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Zoltan Borok-Nagy <[email protected]>
> Blackisting tables does not work with IcebergMetaProvider
> ---------------------------------------------------------
>
> Key: IMPALA-14341
> URL: https://issues.apache.org/jira/browse/IMPALA-14341
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zoltán Borók-Nagy
> Assignee: Jason Fehr
> Priority: Major
> Labels: impala-iceberg, ramp-up
>
> We should make sure that users can still blacklist tables with MetaProviders.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
