[
https://issues.apache.org/jira/browse/NIFI-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937197#comment-17937197
]
David Handermann commented on NIFI-14251:
-----------------------------------------
[~dstiegli1] Yes, adding the {{--enable-native-access=ALL-UNNAMED}} argument in
bootstrap.conf would hide the warning, but since NiFi doesn't use Java modules,
it would apply to any native access from any component. For this reason, adding
the generic flag is not the ideal solution, since it could mask behavior from
other components. It is an acceptable resolution for a manual change to
bootstrap.conf, but it does not seem like the best option as a default setting
in NiFi itself.
> Linker errors printing to System.out create user confusion
> ----------------------------------------------------------
>
> Key: NIFI-14251
> URL: https://issues.apache.org/jira/browse/NIFI-14251
> Project: Apache NiFi
> Issue Type: Task
> Affects Versions: 2.2.0
> Reporter: Joe Witt
> Priority: Major
>
> {noformat}
> WARNING: A restricted method in java.lang.foreign.Linker has been called
> WARNING: java.lang.foreign.Linker::downcallHandle has been called by the
> unnamed module
> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for this
> module
> {noformat}
> Something in our default codebase (Lucene supspected from provenance) is
> causing these warnings now in Java 21 land. We should find out what it is
> and get these warnings to go away by either accepting this and setting
> configs to ignore or avoiding usage of the offending piece (seems less
> likely).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
