You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "nabacg (Jira)" <ji...@apache.org> on 2020/01/29 13:14:00 UTC
[jira] [Comment Edited] (SPARK-12312) JDBC connection to Kerberos
secured databases fails on remote executors
[ https://issues.apache.org/jira/browse/SPARK-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025254#comment-17025254 ]
nabacg edited comment on SPARK-12312 at 1/29/20 1:13 PM:
---------------------------------------------------------
My suggestion was for people who need a working solution now and can't wait till there is a new Spark release out and/or can't easily upgrade their cluster installations (which happens in corporate multi-tenant situations, I've been there.. ).
My approach avoids those problems by patching the JDBC driver, instead of Spark. It's not a long term solution, but perhaps will save someone's skin. I certainly worked for me and one of my clients.
was (Author: nabacg):
My suggestion was for people who need a working solution now and can't wait till there is a new Spark release out and/or can't easily upgrade their cluster installations (which happens in corporate multi-tenant situations, I've been there.. ).
My approach avoids those problems by patching the JDBC driver, instead of Spark. It's not a long term solution, but perhaps will save someone some skin. I certainly worked for me and one of my clients.
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org