[
https://issues.apache.org/jira/browse/SOLR-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036951#comment-16036951
]
David Smiley commented on SOLR-5478:
------------------------------------
Perhaps this issue can be closed now if the ID field can be marked as not
stored but have docValues -- thus a user can simply configure this. I'm not
sure if this is expressly tested? I could be mistaken but I thought Solr had
some expectation somewhere that the uniqueKey be stored, even though nowadays
we have a docValues substitute.
_Separate issues_ would be:
* configuring docValues=true stored=false for the uniqueKey in our default
schemas
* if all "fl" fields requested have docValues and if there is no loss in
functionality (no multi-valued fields) then don't use stored-values at all. My
patch on this issue does this; but it's perhaps broader in scope than handling
just the uniqueKey in the title of this issue. Shrug; or maybe adjust this
issue scope to be broader and keep it open?
> 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.9, 6.0
>
> Attachments: SOLR-5478.patch, SOLR-5478.patch, SOLR-5478 smiley
> fl.fieldCacheFields.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
