[
https://issues.apache.org/jira/browse/NIFI-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721196#comment-16721196
]
ASF GitHub Bot commented on NIFI-5895:
--------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/3218
This PR has been tested against an Oozie 4.2.0 server instance in the
following conditions:
- Plaintext
- Plaintext + SSL
- Kerberos
- Kerberos + SSL
A very basic examples has been used:
https://github.com/apache/oozie/tree/branch-4.3/examples/src/main/apps/shell
Testing workflow:
https://gist.github.com/pvillard31/4a0a7b33dc27c11538cec0b5e80c0324
The workflow.xml from the Oozie repo must be pushed in HDFS in a directory
and that directory is used in the configuration of the processor. All the
properties given in the job.properties file from the Oozie repo must be passed
through the configuration of the processor or the attributes of the flow files.
> Add a processor to start an Oozie workflow
> ------------------------------------------
>
> Key: NIFI-5895
> URL: https://issues.apache.org/jira/browse/NIFI-5895
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> It would be useful to have a processor allowing a user to start an Oozie
> workflow. Typical use case would be: data is pushed to HDFS and user wants to
> start an Oozie workflow that is going to process that data. Using the REST
> API with InvokeHttp is possible but it gets harder when Kerberos is enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
