[
https://issues.apache.org/jira/browse/NIFI-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316246#comment-17316246
]
ASF subversion and git services commented on NIFI-8380:
-------------------------------------------------------
Commit b79987918a3f8e3cb69e3d21176f09704c441707 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b799879 ]
NIFI-8380: Allow for an extensions.directory property to specify where to place
downloaded files. Also fixed an issue that was encountered, when a Source
Processor is scheduled for Primary Node Only but more than 1 task is set. In
that case, even though only a single task will should be scheduled, an
Exception was getting thrown because @OnScheduled methods of Processors were
still called. To avoid this, moved the initialization of the dataflow outside
of the creation of the dataflow so that initialization can be triggered only
when appropriate.
NIFI-8380: Removed requirement in validation for working directory and
extensions directory to exist; removed auto-creation of directories in
validation
NIFI-8380: Fixed a few thrading bugs, so that if we have multiple threads
trying to download/unpack extensions, we properly synchronize the unpacking and
unpack into the correct sub-directory under the working directory
Signed-off-by: Pierre Villard <pierre.villard...@gmail.com>
This closes #4950.
> Stateless NiFi Kafka connector should allow separate directories for
> extensions and base nars
> ---------------------------------------------------------------------------------------------
>
> Key: NIFI-8380
> URL: https://issues.apache.org/jira/browse/NIFI-8380
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We should allow separating out the nar directory and the extensions directory
> so that they are not forced to be co-located. This will make upgrades simpler
> and addresses issues where the user running the connector may not have write
> permissions on the directory where the connector is deployed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
