[SOLR-12625] Combine SolrDocumentFetcher and RetrieveFieldsOptimizer

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.5, 8.0
• Assignee: Erick Erickson
• Reporter: Erick Erickson
• Created: 03/Aug/18 23:57
• Updated: 08/Jun/19 15:00
• Resolved: 20/Aug/18 17:41

Description

We have SolrDocumentFetcher and RetrieveFieldsOptimizer. The
relationship between the two is unclear at first glance. Using
SolrDocumentFetcher by itself is (or can be) inefficient.

WDYT about combining the two? Is there a good reason you would want to
use SolrDocumentFetcher instead of RetrieveFieldsOptimizer?

Ideally I'd want to be able to write code like:

solrDocumentFetcher.fillDocValuesMostEfficiently

That created an optimizer and "did the right thing".

Assigning to myself to keep track, but if anyone feels motivated feel free to take it over.

Issue Links

• is related to: SOLR-12598 Do not fetch non-stored fields
• relates to: SOLR-10816 Change uniqueKey to use docValues and not stored field
• relates to: SOLR-12596 DocValues page should explain terms like SORTED_SET, SORTED_NUMERIC