[ 
https://issues.apache.org/jira/browse/NIFI-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890532#comment-17890532
 ] 

ASF subversion and git services commented on NIFI-13892:
--------------------------------------------------------

Commit 570a3dc71c7f8fa9ab5c27be6169050221e8c18a in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=570a3dc71c ]

NIFI-13892 Suppressed JVM Logging for Lucene Vectorization

Signed-off-by: Pierre Villard <[email protected]>

This closes #9412.


> Suppress JVM Logging from Lucene Classes
> ----------------------------------------
>
>                 Key: NIFI-13892
>                 URL: https://issues.apache.org/jira/browse/NIFI-13892
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>             Fix For: 2.0.0-M5
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Lucene libraries supporting the Provenance Repository log the following 
> messages related to experimental and native access settings at the JVM level.
> {noformat}
> INFO [Index Provenance Events-1] o.a.l.s.MemorySegmentIndexInputProvider 
> Using MemorySegmentIndexInput and native madvise support with Java 21 or 
> later; to disable start with 
> -Dorg.apache.lucene.store.MMapDirectory.enableMemorySegments=false
> WARN [Index Provenance Events-1] o.a.l.i.v.VectorizationProvider Java vector 
> incubator module is not readable. For optimal vector performance, pass 
> '--add-modules jdk.incubator.vector' to enable Vector API.
> {noformat}
> These messages reflect parameters that should be changed for standard 
> operation and can be confusing given the Lucene is an implementation detail 
> of the Provenance Repository. For this reason, these log messages should be 
> suppressed in the default Logback configuration



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to