Repository navigation
[ESQL] Route (LONG,BYTES_REF) through adaptive BlockHash - #152010
Conversation
(LONG,BYTES_REF)/(BYTES_REF,LONG) STATS now uses a new LongBytesRefAdaptiveBlockHash that runs a dict-aware vector-only fast path (BytesRefBlockHash + LongLongHashTable) until a non-vector page arrives, then migrates groups to PackedValuesBlockHash so null/MV handling matches the contract. This re-enables the optimization gated off since elastic#99434 without resurrecting its broken null path. Out of scope: (LONG,LONG) and the 3-key shape.
2d71c6c to
29c723f
Compare
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
(LONG,BYTES_REF)/(BYTES_REF,LONG) STATS now uses a new
LongBytesRefAdaptiveBlockHash that runs a dict-aware vector-only
fast path (BytesRefBlockHash + LongLongHashTable) until a non-vector
page arrives, then migrates groups to PackedValuesBlockHash so
null/MV handling matches the contract. This re-enables the
optimization gated off since #99434 without resurrecting its broken
null path.
Out of scope (separate follow-ups): (LONG,LONG), (INT,BYTES_REF)
family, and the 3-key (LONG,LONG,BYTES_REF) shape.