HoustonPutman commented on pull request #120: URL: https://github.com/apache/solr/pull/120#issuecomment-883620391
> Regarding minio Yeah, I changed a few things and got it closer to working, but I guess that problem was the last and unsolvable hurdle... > Regarding the AwsRegion comment, what is the use case you had in mind? I would say it is at least somewhat common for companies to have S3 compatible alternatives that have to be used in lieu of AWS S3. While it is possible for every company to manage their own plugin, it would be nice to at least have the endpoint configurable for users to try out. If it doesn't work, then nothing lost, they can still create their own. But if it does, then it's a massive weight off their shoulders being able to use the default S3 plugin. We can make it very explicit in the documentation that this is meant to be used with AWS S3, but users are able to use it with S3 compatible endpoints at their own risk, and point out Minio as an example of an S3 compatible option that does not work with the plugin. Another point is that users will have to upgrade the plugin if they want to use new regions that AWS introduces after the version of the AWS SDK we are using was cut, which will probably be painful because the version of the plugin will likely be tied to the version of Solr. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
