You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Gabor Somogyi (Jira)" <ji...@apache.org> on 2020/06/22 08:53:00 UTC
[jira] [Comment Edited] (SPARK-32001) Create Kerberos
authentication provider API in JDBC connector
[ https://issues.apache.org/jira/browse/SPARK-32001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141830#comment-17141830 ]
Gabor Somogyi edited comment on SPARK-32001 at 6/22/20, 8:52 AM:
-----------------------------------------------------------------
cc [~smilegator] [~maropu] this and SPARK-32047 can be interesting to you guys.
Please share your thoughts/concerns if you have.
was (Author: gsomogyi):
cc [~smilegator] [~maropu] this and SPARK-32047 can be interesting to you guys.
Please share your thoughts if you have anything to add or have concerns.
> Create Kerberos authentication provider API in JDBC connector
> -------------------------------------------------------------
>
> Key: SPARK-32001
> URL: https://issues.apache.org/jira/browse/SPARK-32001
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 3.1.0
> Reporter: Gabor Somogyi
> Priority: Major
>
> Adding embedded provider to all the possible databases would generate high maintenance cost on Spark side.
> Instead an API can be introduced which would allow to implement further providers independently.
> One important requirement what I suggest is: JDBC connection providers must be loaded independently just like delegation token providers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org