[
https://issues.apache.org/jira/browse/NIFI-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430084#comment-17430084
]
ASF subversion and git services commented on NIFI-9292:
-------------------------------------------------------
Commit be2b80d9094beeb3a2fa2b6a0ecbee2eb8b0935d in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=be2b80d ]
NIFI-9292: Added getInputPortNames() and getOutputPortNames() to
StatelessDataflowDefinition and getReadOnlyExtensionsDirectories() to
StatelessEngineConfiguration
- Addressed issue identified in system test where a flow can fail due to
FailurePortEncounteredException but then purge the flow in the background after
the call to trigger completes
Signed-off-by: Joe Gresock <[email protected]>
This closes #5450.
> Expose names of ports from StatelessDataflowDefinition and allow multiple
> extension directories
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-9292
> URL: https://issues.apache.org/jira/browse/NIFI-9292
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Stateless
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The StatelessDataflowDefinition class is generic, so it can potentially hold
> a flow that is comprise of a {{byte[]}}, a {{VersionedFlowSnapshot}}, etc.
> But this makes it difficult to know the names of Input Ports & Output Ports.
> We currently expose the names of configured Failure Ports but should expose
> the names of all Input Ports and Output Ports that are a part of the
> dataflow, as well.
> Additionally, in improving this configuration API, we should allow for
> multiple Extensions directories to be specified. Currently, we allow for the
> NAR directory to be specified, which is the location of the stateless nar
> itself and supporting libraries. We also expose a configuration option for an
> Extensions directory. But if there are missing extensions, the Extensions
> directory is used to write those extensions when they are downloaded. This
> means that we cannot mount a read-only volume that contains extensions. This
> would be helpful when running in some cloud environments where we may have
> access to multiple read-only directories.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
