[
https://issues.apache.org/jira/browse/SOLR-15707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436089#comment-17436089
]
ASF subversion and git services commented on SOLR-15707:
--------------------------------------------------------
Commit 55a0a4140803e713ff06f9dc5486b00dab81ea85 in lucene-solr's branch
refs/heads/branch_8x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=55a0a41 ]
SOLR-15707: Add the ability to set the AWS Profile per S3Repository (#357)
Updating the AWS SDK version for better retry options.
> Ability to set the AWS Profile for each S3Repository
> ----------------------------------------------------
>
> Key: SOLR-15707
> URL: https://issues.apache.org/jira/browse/SOLR-15707
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - S3 Repository
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The S3Repository makes use of the default settings of the AWS Java SDK. Many
> of these settings are able to be overwritten in the AWS configuration file.
> However, if a user has multiple S3Repositories defined, then they might want
> to set different settings for each repository.
> With the EnvVar, system property approach, you can only set 1 value for each
> setting, so all uses of S3Repository will use the same values for a Solr
> cloud. One way of getting around this, and not requiring all settings to be
> overridable via the solr.xml, is to allow users to set the AWS profile for
> each S3Repository. This will allow them to set independent settings
> per-profile in the AWS configuration file, then specify which S3Repositories
> should use which profile.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
