Re: [I] Document how Polaris works with different cloud storage(S3, Azure Blob Storage, GCS). [polaris]

["mj006648 (via GitHub)" <gi...@apache.org>]

mj006648 commented on issue #1325:
URL: https://github.com/apache/polaris/issues/1325#issuecomment-4447111795

   Hi @flyrain, following up on your note that more docs are needed for storage backends beyond what landed in #1435. If no one is currently working on the Azure Blob Storage and GCS sides, I'd like to pick those up.
   
   Tentative plan, mirroring the structure of the existing S3 / Spark docs:
   
   - Azure Blob Storage configuration page
     - `STORAGE_CONFIG_INFO` example (tenant id, client id, secret vs. Workload Identity)
     - ADLS Gen2 endpoint conventions
     - Vended Credentials behavior (cross-ref to #418 if still relevant)
   - Google Cloud Storage configuration page
     - service-account-key vs. ADC vs. HMAC
     - uniform vs. bucket-level IAM notes
   - A short section on the client-side dependencies each backend needs (hadoop-azure, gcs-connector, etc.) when used via Spark / Trino / PyIceberg.
   
   Does this match what you had in mind, or would you prefer a single consolidated "storage backends" page instead of per-backend pages? Happy to follow whichever structure fits the existing docs better.


-- 
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-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org