[
https://issues.apache.org/jira/browse/NIFI-16410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121322#comment-18121322
]
ASF subversion and git services commented on NIFI-16410:
--------------------------------------------------------
Commit 59fb260d7a03c4653f3f85280c84aab339123e91 in nifi's branch
refs/heads/main from Kevin Doran
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=59fb260d7a0 ]
NIFI-16410 Log single-match NAR dependency fallback at INFO (#11743)
Keep dependency substitution visible without warning when the loader
selects the sole available candidate and continues. Apply the same level
to startup and additional NAR loading; leave failure diagnostics unchanged.
> Log single-match NAR dependency fallback at INFO instead of WARN
> ----------------------------------------------------------------
>
> Key: NIFI-16410
> URL: https://issues.apache.org/jira/browse/NIFI-16410
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When NiFi cannot find the exact declared NAR dependency but finds a single
> alternative matching the dependency ID, it uses that dependency and continues
> loading. This supported fallback currently logs at WARN:
> While loading 'org.example:example-processors-nar:1.1.0' unable to locate
> exact NAR dependency 'org.example:example-api-nar:1.1.0'. Only found one
> possible match 'org.example:example-api-nar:1.0.0'. Continuing...
> Change this message to INFO in both startup loading and additional NAR
> loading in {{{}NarClassLoaders{}}}. This keeps the dependency substitution
> visible without presenting it as a loading failure.
> Dependency resolution behavior and warnings for unresolved dependencies
> remain unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
