[
https://issues.apache.org/jira/browse/LUCENE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015582#comment-14015582
]
Robert Muir commented on LUCENE-5703:
-------------------------------------
{quote}
The term returned by TermsEnum.next() or TermsEnum.term() always comes from
Sorted(Set)DocValues.lookupOrd. It doesn't allocate its own terms.
{quote}
Well only in the base (simplistic) implementation. At least for the default
codec, the codec overrides TermsEnum and implements it special for performance
reasons. and lookupOrd in this case actually uses the termsenum (i think)
> Don't allocate/copy bytes all the time in binary DV producers
> -------------------------------------------------------------
>
> Key: LUCENE-5703
> URL: https://issues.apache.org/jira/browse/LUCENE-5703
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Fix For: 4.9, 5.0
>
> Attachments: LUCENE-5703.patch
>
>
> Our binary doc values producers keep on creating new {{byte[]}} arrays and
> copying bytes when a value is requested, which likely doesn't help
> performance. This has been done because of the way fieldcache consumers used
> the API, but we should try to fix it in 5.0.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
