[
https://issues.apache.org/jira/browse/SOLR-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-10273:
--------------------------------
Attachment: SOLR_10273_DocumentBuilder_move_longest_to_last.patch
Here's a patch with test. It also incorporates a minimum long length of 1024
that is overrideable via {{solr.docBuilder.minLengthToMoveLast}} (an internal
unsupported setting). If no field is at least that long then it won't bother
moving it. In tests temporarily I set this to 0 and no existing test broke,
which is a good sign. If someone were to observe the ordering that fields come
back from Solr with a '*', they might notice a change in ordering after this.
Of course people shouldn't depend on inter-field ordering.
> Re-order largest field values last in Lucene Document
> -----------------------------------------------------
>
> Key: SOLR-10273
> URL: https://issues.apache.org/jira/browse/SOLR-10273
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 6.5
>
> Attachments: SOLR_10273_DocumentBuilder_move_longest_to_last.patch
>
>
> (part of umbrella issue SOLR-10117)
> In Solr's {{DocumentBuilder}}, at the very end, we should move the field
> value(s) associated with the largest field (assuming "stored") to be last.
> Lucene's default stored value codec can avoid reading and decompressing the
> last field value when it's not requested. (As of LUCENE-6898).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
