[
https://issues.apache.org/jira/browse/SOLR-15599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405425#comment-17405425
]
Houston Putman commented on SOLR-15599:
---------------------------------------
With the v2 api we have a choice for the HttpClient used.
We are sticking with a synchronous client (Apache) in this ticket. I'm fine
switching to async in the future, but I'd rather we limit the scope of this
ticket.
The only non-supported option between apache (sync) and netty (async) is that
we are using the {{useSystemPropertyValues}} option provided by apache. If we
move to netty in the future, we would just need to make sure to check the
system properties ourselves and set the appropriate proxy options manually for
the user.
Otherwise we can convert {{proxyUrl}} to {{host}}, {{port}} and {{scheme}}
ourselves very easily. (another difference between apache and netty)
> Upgrade AWS SDK from v1 to v2 for the S3 Repository
> ---------------------------------------------------
>
> Key: SOLR-15599
> URL: https://issues.apache.org/jira/browse/SOLR-15599
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - S3 Repository
> Affects Versions: 8.10
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently the s3-repository contrib relies on the {{javax.xml.bind:jaxb-api}}
> dependency, which isn't allowed in the Solr/Lucene-Solr project.
> As per the comments made in the original commit, this dependency can be
> removed if we upgrade the AWS SDK to v2. This should help in future-proofing
> the contrib module as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
