Only use MemorySegment scorers when slices can be obtained from the IndexInput#145343
Only use MemorySegment scorers when slices can be obtained from the IndexInput#145343jimczi merged 4 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
|
Hi @thecoop, I've created a changelog YAML for you. |
🔍 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?
|
…ndexInput (elastic#145343) * Only use MemorySegment scorers when slices can be obtained from the IndexInput --------- Co-authored-by: Benjamin Trent <ben.w.trent@gmail.com>
Uses the fallback behaviour to single-scoring bulk implementations modified by #141718 (with interactions with #141762 too)