[
https://issues.apache.org/jira/browse/SPARK-32001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143007#comment-17143007
]
Gabor Somogyi commented on SPARK-32001:
---------------------------------------
With the service loader no registration is needed and everything works like
charm.
Additionally harder to implement enable flag. Let me give an example:
With JdbcDiaclect: one creates a dialect class and then in the app
"JdbcDialects.registerDialect(new CustomDialect())" must be called.
With ServiceLoader: one creates a provider class + META-INF.services file (no
registration or whatever needed)
Not super experienced in the dialect area so it may be needed per app but
kerberos authentication provider is not something what the user needs to care
about in the app code. The company must write one provider, put it on the
classpath of Spark and must be forgotten.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
