[
https://issues.apache.org/jira/browse/SPARK-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025176#comment-17025176
]
nabacg commented on SPARK-12312:
--------------------------------
I originally got around this problem using the approach sketched in this repo:
[https://github.com/nabacg/krb5sqljdb]
Hope it might help someone.. it saved my project from missing an important
deadline when we discovered this issue. Unfortunately as you say it's not very
well documented and you often tend to discover this problem in later stage of
the project, like when moving from DEV to UAT/PROD..
> JDBC connection to Kerberos secured databases fails on remote executors
> -----------------------------------------------------------------------
>
> Key: SPARK-12312
> URL: https://issues.apache.org/jira/browse/SPARK-12312
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.2, 2.4.2
> Reporter: nabacg
> Priority: Minor
>
> When loading DataFrames from JDBC datasource with Kerberos authentication,
> remote executors (yarn-client/cluster etc. modes) fail to establish a
> connection due to lack of Kerberos ticket or ability to generate it.
> This is a real issue when trying to ingest data from kerberized data sources
> (SQL Server, Oracle) in enterprise environment where exposing simple
> authentication access is not an option due to IT policy issues.
--
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
