[
https://issues.apache.org/jira/browse/KUDU-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840351#comment-15840351
]
Todd Lipcon commented on KUDU-1738:
-----------------------------------
[~sailesh] this seems necessary for Impala/Kudu integration to not break, right?
> Allow users of C++ client to disable initialization of OpenSSL
> --------------------------------------------------------------
>
> Key: KUDU-1738
> URL: https://issues.apache.org/jira/browse/KUDU-1738
> Project: Kudu
> Issue Type: Bug
> Components: client, security
> Affects Versions: 1.1.0
> Reporter: Todd Lipcon
>
> As we start to use OpenSSL from within the client, we now take care of
> initializing the OpenSSL library. Programs which embed us may have already
> initialized OpenSSL for their own purposes. In that case, we don't want Kudu
> to run the initialization a second time.
> We should probably add some kind of option to KuduClientBuilder which
> disables the SSL initialization. Another thought is that we may want to
> detect if the SSL library has already been initialized and automatically
> skip. (it seems this is possible by calling SSL_CTX_new and checking the
> error code to see if it's not initialized yet)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
