You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2015/12/01 18:09:11 UTC

[jira] [Comment Edited] (SOLR-8344) Decide default when requested fields are both column and row stored.

    [ https://issues.apache.org/jira/browse/SOLR-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034083#comment-15034083 ] 

Yonik Seeley edited comment on SOLR-8344 at 12/1/15 5:08 PM:
-------------------------------------------------------------

bq. Not quite sure what to do if the user defines both however, perhaps use the stored value?
That's what this issue is about.

bq. Why are we trying to anticipate "the right thing to do"?
They are both "right" (semantically equivalent), so we're trying to figure out the best performing option.  That will change based on the request, and always (statically) choosing one over the other is never going to be optimal.

Example: If a field is column-stored (docValued), one could chose to add it as stored so that it would be quicker to retrieve along with other non-docvalue fields (if you need to go to stored fields anyway, just get all the field values you can from there).  But when accessing that field alone, we'd still certainly want to use the column... it will be much faster.



was (Author: yseeley@gmail.com):
Followup of https://issues.apache.org/jira/browse/SOLR-8220?focusedCommentId=15034013&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15034013

bq. Not quite sure what to do if the user defines both however, perhaps use the stored value?
That's what this issue is about.

bq. Why are we trying to anticipate "the right thing to do"?
They are both "right" (semantically equivalent), so we're trying to figure out the best performing option.  That will change based on the request, and always (statically) choosing one over the other is never going to be optimal.

Example: If a field is column-stored (docValued), one could chose to add it as stored so that it would be quicker to retrieve along with other non-docvalue fields (if you need to go to stored fields anyway, just get all the field values you can from there).  But when accessing that field alone, we'd still certainly want to use the column... it will be much faster.


> Decide default when requested fields are both column and row stored.
> --------------------------------------------------------------------
>
>                 Key: SOLR-8344
>                 URL: https://issues.apache.org/jira/browse/SOLR-8344
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ishan Chattopadhyaya
>
> This issue was discussed in the comments at SOLR-8220. Splitting it out to a separate issue so that we can have a focused discussion on whether/how to do this.
> If a given set of requested fields are all stored and have docValues (column stored), we can retrieve the values from either place.  What should the default be?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org