[
https://issues.apache.org/jira/browse/SOLR-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407547#comment-13407547
]
Uwe Schindler commented on SOLR-3595:
-------------------------------------
Multivalued does not work with fields that consist of more than one Lucene
field behind, because the field vales cannot be corelated. We should disallow
multi value and throw exception. This is similar to LatLong fields I think.
> Currency types do not support range queries when multiValued
> ------------------------------------------------------------
>
> Key: SOLR-3595
> URL: https://issues.apache.org/jira/browse/SOLR-3595
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 4.0-ALPHA
> Reporter: Erick Erickson
> Priority: Minor
>
> You can define the currency type as multiValued. However, if you do (and have
> more than one value), range queries, at least, do not work. See the thread
> titled "Filtering a query by range returning unexpected results".
> I'm not at all sure that currency type _should_ support multivalued. For
> instance, how would one handle storing multiple values for a currency type in
> different currencies (e.g. USD and EUR)? I don't know enough about the
> internals to understand if it's possible, this JIRA is the result of a
> question on the users list.
> If we decide that currency should _not_ support multiValued, it seems a check
> at startup is in order on the "fail early, fail loudly" principle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
