feat: Suppress JVM warnings from Lucene within CLI #8003
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chadlwilson
force-pushed
the
fix-jvm-warning-logs
branch
from
c2707ae to
ecbee4b
Compare
chadlwilson
changed the title
Signed-off-by: Chad Wilson <[email protected]>
chadlwilson
force-pushed
the
fix-jvm-warning-logs
branch
from
ecbee4b to
973511b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Follow-up to #7979 to remove remaining JVM warnings from the normal log output on JDK 21/25 CLI/Docker usage.
Alternate is to consider the use of all of these native Lucene features and whether it is worthwhile given the
scale of ODC's Lucene usage. (e.g the vector API probably isn't accessible/usable right now)
Related issues
Have test cases been added to cover the new functionality?
no