[
https://issues.apache.org/jira/browse/RANGER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831868#comment-16831868
]
Srikanth Venkat commented on RANGER-2128:
-----------------------------------------
I have several questions on this:
1) What is the use case we are trying to solve here? Is it using the Spark
catalog with Ranger AuthZ? Or is this for the use case where there is no Hive
metastore and Spark has its own catalog (I believe this is the case with Hive3+
and in the more recent Spark2.3+ if I remember correctly)
2) Where is this plugin deployed? Will it work on kerberized clusters?
3) What specifically are differences in what is supported between this plugin
and the current Ranger-Hive Authorizer? What versions of Spark, Hive and Ranger
will this require?
4) There are pointers to another github project
[https://github.com/yaooqinn/kyuubi] in the thread above which appears to be an
enhanced version of SparkThrift Server. It would be good to understand whether
that has Apache 2 compatible licenses and whether kyuubi has to be included
into an existing Spark deployment directly or via external dependencies for
this Spark SQL Ranger plugin to work? If there is a requirement to have Kyuubi
vesion deployed in a cluster on top of Spark2 then does anyone know whether
there is any plan to add this directly into Spark2 project first class? It
becomes more difficult to certify against such clones of core services in
another Apache project if the mainstream Spark2 project is not supporting this
enhanced version.
Can we clarify the above items these please?
> Implement SparkSQL plugin
> -------------------------
>
> Key: RANGER-2128
> URL: https://issues.apache.org/jira/browse/RANGER-2128
> Project: Ranger
> Issue Type: New Feature
> Components: plugins, Ranger
> Affects Versions: 1.1.0
> Reporter: t oo
> Assignee: Kent Yao
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: support_ranger11.tgz
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Implement SparkSQL plugin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)