[
https://issues.apache.org/jira/browse/NIFI-13824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893087#comment-17893087
]
ASF subversion and git services commented on NIFI-13824:
--------------------------------------------------------
Commit 3b3e74d46bc81482e7ef40a1088852e3901894c8 in nifi's branch
refs/heads/main from Ferenc Gerlits
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3b3e74d46b ]
NIFI-13824 Installed Python Processor Dependencies with one command
If a Python processor defines dependencies both inline and in a
requirements.txt file, then we need to install the two groups of
dependencies in a single `pip install` command, otherwise pip is
not able to resolve the web of dependencies correctly.
- Added setup-python step with Python 3.12 to ci-workflow for consistent
version behavior
This closes #9429
Signed-off-by: David Handermann <[email protected]>
> Install Python processor dependencies in one go
> -----------------------------------------------
>
> Key: NIFI-13824
> URL: https://issues.apache.org/jira/browse/NIFI-13824
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Ferenc Gerlits
> Assignee: Ferenc Gerlits
> Priority: Minor
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Dependencies for Python processors are defined in two places: the
> {{requirements.txt}} file in the package directory and the
> {{ProcessorDetails.dependencies}} field in the processor class. Currently,
> NiFi first installs the dependencies defined in the former, and then
> separately those defined in the latter.
> This is a problem, because a dependency in the second batch may depend on
> e.g., {{somepackage<2.0}} and if the first batch has already installed
> version {{2.3}} of {{{}somepackage{}}}, then the installation will fail.
> In almost all cases, {{pip}} can find dependency versions which satisfy both
> sets of dependencies, but only if they are all listed in a single {{pip
> install}} command. So we need to merge the two sets of dependencies and
> install them in one go.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
