added support paths to file with wildcard (*) for minio #67
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When Iceberg tables are configured to use MinIO as the object store, users cannot access objects with the s3:// prefix — MinIO requires the use of http:// or https:// endpoints.
However, the current implementation of the Altinity Ice CLI only supports wildcard expansion (*) for paths with the s3:// scheme, using the AWS SDK.
This PR introduces MinioWildcard support that enables wildcard path expansion for HTTP/HTTPS endpoints.
It adds a new internal helper:
com.altinity.ice.cli.internal.http.MinioWildcardwhich performs
?list-type=2&prefix=...requests directly against the MinIO REST API and extracts all matching object keys from XML responses.