maytasm3 opened a new pull request #9375: Add support for optional cloud (aws, 
gcs, etc.) credentials for s3 for ingestion
URL: https://github.com/apache/druid/pull/9375
 
 
   Add support for optional cloud (aws, gcs, etc.) credentials for s3 for 
ingestion
   
   ### Description
   
   Cloud InputSource (such as S3, etc.) should be able to support taking in 
credentials optionally in order to be able to read from multiple 
buckets/location. This is in order to use different credentials than the 
default (i.e. the one provided in the common runtime property) and also to be 
able to use different credentials for each ingestion.
   
   This address the proposal https://github.com/apache/druid/issues/9305
   
   Motivation
   
   This PR has:
   - [ ] been self-reviewed.
      - [ ] using the [concurrency 
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
 (Remove this item if the PR doesn't have any relation to concurrency.)
   - [ ] added documentation for new or modified features or behaviors.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/licenses.yaml)
   - [ ] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [ ] added unit tests or modified existing tests to cover new code paths.
   - [ ] added integration tests.
   - [ ] been tested in a test Druid cluster.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to