[
https://issues.apache.org/jira/browse/SOLR-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867869#comment-13867869
]
Manuel Lenormand edited comment on SOLR-5478 at 1/10/14 3:00 PM:
-----------------------------------------------------------------
The problem is that the searcher that I get in the BinaryResponseWriter exposes
the atomic reader as SlowCompositeWrapper.
The new patch involves in creating the SlowCompositeWrapper (shard level) only
once per commit, and as these docValues are saved on disk there is no
duplication.
how do you suggest accessing the per-segment docValues reader? Where would the
docId-->UniqueKey convesation be done?
was (Author: manuel lenormand):
The problem is that the searcher that I get in the BinaryResponseWriter exposes
the atomic reader as SlowCompositeWrapper.
The new patch involves in creating the SlowCompositeWrapper (shard level) only
once per commit, and as these docValues are saved on disk there is no
duplication.
how do you suggest accessing the per-segment docValues reader?
> Speed-up distributed search with high rows param or deep paging by
> transforming docId's to uniqueKey via memory docValues
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5478
> URL: https://issues.apache.org/jira/browse/SOLR-5478
> Project: Solr
> Issue Type: Improvement
> Components: Response Writers
> Affects Versions: 4.5
> Reporter: Manuel Lenormand
> Fix For: 4.7
>
> Attachments: SOLR-5478.patch, SOLR-5478.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
