You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2016/03/09 21:13:40 UTC
[jira] [Updated] (SOLR-8813) Add test for MultiValued fields being
returned in the correct order
[ https://issues.apache.org/jira/browse/SOLR-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson updated SOLR-8813:
---------------------------------
Attachment: SOLR-8813.patch
Note that I removed the <fields> and <types> tags from the schema file and re-indented.
The only substantive change to the schema is adding four very specific types...
> Add test for MultiValued fields being returned in the correct order
> -------------------------------------------------------------------
>
> Key: SOLR-8813
> URL: https://issues.apache.org/jira/browse/SOLR-8813
> Project: Solr
> Issue Type: Improvement
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Attachments: SOLR-8813.patch
>
>
> This is an outgrowth of SOLR-8740. When we move to returning fields in the response from docValues fields, we _may_ break the contract we've had for years that multiValued stored fields are returned in the order they were inserted.
> This test is here it show the current behavior. If we change the behavior we need to clearly document any breaks in back-compat.
--
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