Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18385
Can one of the admins verify this patch?
---
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 feat
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18385
It indeed used in Spark code `SSLOptions`, for example ssl port is used to
specify https port for https live and history UI. Also `needClientAuth` is used
for mutual authentication. I'm not sure w
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18385
@jerryshao
Thanks for your reply.I didn't notice "spark.ssl" has been replaced by $ns
inSSLOptions,it is my fault.But I still have a question,whether
"spark.ssl.[namespace].port" should be
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18385
Sorry I cannot get your point?
>But I still have a question,whether "spark.ssl.[namespace].port" should be
modify to "spark.ssl.port" to meet the naming style of others?
---
If your proj
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18385
@jerryshao
Sorry,my English is poor.I mean whether we should change the configuration
which named "spark.ssl.[namespace].port" to "spark.ssl.port".
---
If your project is set up for it, y
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18385
Can you please point where do we change from "spark.ssl.[namespace].port"
to "spark.ssl.port"?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18385
@jerryshao
Ok, I get it.
---
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 a
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18385
This should be closed
---
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,
