Skip to content

Conversation

trina242
Copy link

@trina242 trina242 commented Sep 30, 2025

Disclaimer

This PR is an updated version of #26287, as it can't be reopened because of the force-push (rebase).

Description

This PR decouples generic (not S3-related) security mapping code from S3 filesystem into a new library trino-iam-aws, as well as adds security mapping support for Glue metastore.

Additional context and related issues

Related issue: #26286

I'm open to any suggestions related to this implementation, especially when it comes to config parameters - I've been a bit uncomfortable with duplicating so much, but it makes more sense to me than mixing parameters from base class and subclass (like iam.security-mapping.config-file and s3.security-mapping.kms-key-id-credential-name).

This is my first contribution to Trino, while Java definitely not being my favourite language, so please get easy on me! 😉

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
(x) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

@github-actions github-actions bot added the delta-lake Delta Lake connector label Sep 30, 2025
@trina242 trina242 requested a review from electrum October 1, 2025 10:44
@findepi findepi changed the title #26286: Decoupled IAM security mapping from s3 filesystem and added Glue support Decouple IAM security mapping from S3 filesystem and add Glue support Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed delta-lake Delta Lake connector docs hive Hive connector iceberg Iceberg connector
Development

Successfully merging this pull request may close these issues.

1 participant