switch default front-coding format to v1, drop experimental from docs#18984
Open
clintropolis wants to merge 4 commits intoapache:masterfrom
Open
switch default front-coding format to v1, drop experimental from docs#18984clintropolis wants to merge 4 commits intoapache:masterfrom
clintropolis wants to merge 4 commits intoapache:masterfrom
Conversation
capistrant
reviewed
Feb 5, 2026
Contributor
capistrant
left a comment
capistrant
left a comment
There was a problem hiding this comment.
left suggestion to nuke another experimental reference
Co-authored-by: Lucas Capistrant <capistrant@users.noreply.github.com>
capistrant
approved these changes
Feb 5, 2026
Contributor
|
Added upgrade note label to remind ourselves to callout for folks who may be using v0 and upgrading from < druid 26 |
Contributor
which would be an insane jump, so I'd bet very unlikely. ps sorry about the close open. clicking buttons to fast I guess |
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
2 participants
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.
This PR bumps the default front-coded format to V1, which has a number of improvements over V0, but couldn't immediately be the default due to backwards compatibility concerns. V1 has been in Druid since 26 release, so I think it is plenty safe to switch the default at this point, however anyone upgrading from a version older than this and also using front-coding might want to take note of this and plan accordingly for upgrade to make downgrades not be tricky.
The docs are also updated to drop the 'experimental' wording around this feature, as it has been included and in use for quite some time. I've also removed some stuff in the release/upgrade notes about it being on by default, since it is not. We can add that info there at some future time, if that ever comes to pass where we make it the default.
With regards to making it the default, I think my preference would be to have an 'auto' mode where it takes statistics during indexing to determine if front-coding would be effective, and if so, automatically pick an ideal bucket size.