Avoid selecting unrelated schemas from the information_schema #11855
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
io.trino.plugin.iceberg.TestSharedHiveMetastore
is based on AWS Glue. When trying to select all the table schemas on which is found a table namedregion
ornation
the routine may find a lot of unrelated schemas.Moreover in the context of enabled table redirections, the tables retrieved for listing are inspected one by one in
MetadataManager#listTables
method. If one of the tables to be inspected, gets dropped, the testio.trino.plugin.iceberg.BaseSharedMetastoreTest#testReadInformationSchema
fails.This is not a fix for the issue, but rather a patch to avoid having the Glue test which rely on shared metastore infrastructure to fail.
Related issues
#9400
PR fixing this issue #11790