Add known issues for Javascript#17716
Closed
adarshsanjeev wants to merge 1 commit intoapache:masterfrom
Closed
Conversation
kfaraz
reviewed
Feb 12, 2025
|
|
||
| ## Known issues | ||
|
|
||
| - Javascript tiered broker selector strategy and Javascript filters currently do not work on Java 17. |
Contributor
There was a problem hiding this comment.
Maybe also mention the corresponding Druid versions where javascript filters wouldn't work since we have dropped support for JDK 8 and 11.
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
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.
Java 17 does not support Javascript as support for the Nashorn JavaScript Engine was dropped. Till #14795 is merged, Javascript tiered broker selector strategy and Javascript filter would not work in Java 17. This PR documents this as a known issue.
This PR has: