[
https://issues.apache.org/jira/browse/NIFI-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372837#comment-16372837
]
ASF GitHub Bot commented on NIFI-4683:
--------------------------------------
Github user jomach commented on the issue:
https://github.com/apache/nifi/pull/2339
hi Guys, this is a great change ! I know that the concept from nifi does
not want it but yeah is life. :)
One question I have what if the Livy server has Kerberos active where can
I give it a keytab to the controlerservice ?
> Add ability to execute Spark jobs via Livy
> ------------------------------------------
>
> Key: NIFI-4683
> URL: https://issues.apache.org/jira/browse/NIFI-4683
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.5.0
>
>
> Proposal for a new feature to enable NiFi users to execute Spark jobs. A
> natural entry point for this is to use Apache Livy, as it is a "REST service
> for Apache Spark". This would allow NiFi to submit Spark jobs without needing
> to bundle a Spark client itself (and maintain versions of Spark, e.g.).
> Some of the components that could be involved include:
> LivySessionController Controller Service (CS) - provides connections to
> available sessions in Livy
> * Users could request a type of connection or to retrieve the same connection
> back by session id if available.
> * Properties to configure Livy session such as number of executors, memory
> * Property for connection pool size
> * Will interact with Livy ensure that only connections that are
> idle/available are added to the pool and checked back in
> * Key for pool could be based on session id or type
> * Ensure to provide any user credentials
> * Leverages SSLContext for security
> LivyProcessor
> * Obtains Spark JARs/files via properties and/or flow file attribute(s)
> * Obtains connection information from LivySessionController
> * Provides attributes to configure session, maintain session id, attach to
> session id
> * Potential advanced UI available for testing code (probably a follow-on Jira)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
