[
https://issues.apache.org/jira/browse/HADOOP-16346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978655#comment-16978655
]
Sahil Takiar commented on HADOOP-16346:
---------------------------------------
I'm going to take another stab at testing this. Will run much more thorough
tests than last time :) - I'm hoping the recent Wildfly release + AWS SDK
upgrade resolved the issue we were seeing. Last time I was able to reproduce
this in Impala, let's see if that is still the case.
> Stabilize S3A OpenSSL support
> -----------------------------
>
> Key: HADOOP-16346
> URL: https://issues.apache.org/jira/browse/HADOOP-16346
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Sahil Takiar
> Priority: Blocker
>
> HADOOP-16050 switched S3A to trying to use OpenSSL. We need to make sure this
> is stable, that people know it exists and aren't left wondering why things
> which did work have now stopped. Which, given I know who will end up with
> those support calls, is not something I want.
> * Set the default back to the original JDK version.
> * Document how to change this so you don't need to use an IDE to work out
> what other values are allowed
> * core-default.xml to include the default value and the text listing the
> other options.
> + anything else
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]