Github user lpiepiora commented on the pull request:
https://github.com/apache/spark/pull/9306#issuecomment-163237036
@steveloughran yes, that's exactly what happened to me in this PR. I wanted
to fix it but, in general as you've said this just yields more problems on
multiple levels.
However s3a is not a breeze either (even in newer Hadoop 2.7+ versions),
especially with Frankfurt buckets, which support only AWS Signature V4.
I'll close this PR anyway, because I think this is not the right way either
(even though this jets3t update was a minor one it upgraded transitive
dependencies, which yielded multiple issues).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
