[
https://issues.apache.org/jira/browse/NIFI-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937192#comment-17937192
]
Daniel Stieglitz edited comment on NIFI-14251 at 3/20/25 6:46 PM:
------------------------------------------------------------------
[~joewitt] Looks like Apache Jena had the same issue as seen
[here|https://github.com/apache/jena/issues/2533]
They added to the command line
{code:java}
--enable-native-access=ALL-UNNAMED --add-modules jdk.incubator.vector{code}
as seen in the following [commit|https://github.com/apache/jena/pull/2782/files]
although they were dealing with a different Lucene version the commonality is
the use of Java 21.
was (Author: JIRAUSER294662):
[~joewitt] Looks like Apache Jena had the same issue as seen
[here|https://github.com/apache/jena/issues/2533]
They added to the command line
{code:java}
--enable-native-access=ALL-UNNAMED --add-modules jdk.incubator.vector{code}
as seen in the following [commit|https://github.com/apache/jena/pull/2782/files]
> 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)
