feat: DH-18364: Add Property to Disable Core DataIndex #6538
Conversation
This file contains 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
rcaudy
added
DocumentationNeeded
ReleaseNotesNeeded
devinrsmith
reviewed
Jan 8, 2025
| * If set to true, then permit where filters to use a data index, when applicable. If false, data indexes are not | ||
| * used even if present. | ||
| */ | ||
| public static boolean USE_DATA_INDEX_FOR_WHERE = |
There was a problem hiding this comment.
Yes. Configuration properties are less than pleasant in Core+ until San Luis; so you can make your script set this if you need it as an alternative to configuring a JVM profile to set a system property from the controller or update a property file across all nodes in the cluster.
rcaudy
approved these changes
Jan 8, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.