[
https://issues.apache.org/jira/browse/LUCENE-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301820#comment-17301820
]
Robert Muir commented on LUCENE-9796:
-------------------------------------
It may be calling the wrong type of SortField (STRING vs STRING_VAL) IIRC.
Sorry you are having trouble with solr, and thank you for working on it.
I am test-driven about such refactorings, and it is difficult/impossible for me
to help with my tiny 2-core laptop (the solr tests run forever). As a side
note, I did try Mark Miller's branch and the tests there are quite usable and
run as fast as lucene tests, so it might be a way to help make life easier.
> fix SortedDocValues to no longer extend BinaryDocValues
> -------------------------------------------------------
>
> Key: LUCENE-9796
> URL: https://issues.apache.org/jira/browse/LUCENE-9796
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Priority: Major
> Fix For: main (9.0)
>
> Attachments: LUCENE-9796.patch, LUCENE-9796_prototype.patch
>
>
> SortedDocValues give ordinals and a way to derefence ordinal as a byte[]
> But currently they *extend* BinaryDocValues, which allows directly calling
> {{binaryValue()}}.
> This allows them to act as a "slow" BinaryDocValues, but it is a performance
> trap, especially now that terms bytes may be block-compressed (LUCENE-9663).
> I think this should be detangled to prevent performance traps like
> LUCENE-9795: SortedDocValues shouldn't have the trappy inherited
> {{binaryValue()}} method that implicitly derefs the ord for the doc, then the
> term bytes for the ord.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
