[SOLR-10255] Large psuedo-stored fields via BinaryDocValuesField

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.7
• Labels: pull-request-available
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 09/Mar/17 06:02
• Updated: 25/Oct/24 17:18
• Resolved: 17/Jul/24 22:19

Description

(sub-issue of SOLR-10117) This is a proposal for a better way for Solr to handle "large" text fields. Large docs that are in Lucene StoredFields slow requests that don't involve access to such fields. This is fundamental to the fact that StoredFields are row-stored. Worse, the Solr documentCache will wind up holding onto massive Strings. While the latter could be tackled on it's own somehow as it's the most serious issue, nevertheless it seems wrong that such large fields are in row-stored storage to begin with. After all, relational DBs seemed to have figured this out and put CLOBs/BLOBs in a separate place. Here, we do similarly by using, Lucene BinaryDocValuesField. BDVF isn't well known in the DocValues family as it's not for typical DocValues purposes like sorting/faceting etc. The default DocValuesFormat doesn't compress these but we could write one that does.

Issue Links

• is duplicated by: SOLR-14454 support for UTF-8 (string) types with DocValuesType.BINARY
• is part of: SOLR-10117 Big docs and the DocumentCache; umbrella issue
• is related to: SOLR-10286 Declare a field as "large", don't keep value in the document cache
• links to: GitHub Pull Request #2536