sathesuraj commented on issue #2207:
URL: https://github.com/apache/polaris/issues/2207#issuecomment-3219681238
@dimas-b -
Please confirm my understanding below and help me with a query.
Setup - Polaris Catalog is running on-prem and we have Non-AWS S3 Compatible
Storage Service:
Understanding summary:
1. If the object storage service supports STS, use the 1.1.0 release and
utilize the new storageConfig properties to create a catalog.
2. If the object storage service does not support STS:
- Use polaris.features."SKIP_CREDENTIAL_SUBSCOPING_INDIRECTION"=true,
and Polaris will use its key and secret set in environment variables.
- Wait for the S3 remote signing feature in the Polaris catalog.
Query:
When we use polaris.features."SKIP_CREDENTIAL_SUBSCOPING_INDIRECTION"=true,
the storageConfigInfo is ignored. In this case, how can we make Polaris use
path-style access?
Additional Context:
I am trying to run Polaris on-prem and not in a cloud environment, but I can
set the S3 key ID and access key to make an S3 connection.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@polaris.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
