[
https://issues.apache.org/jira/browse/SOLR-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337865#comment-14337865
]
David Smiley commented on SOLR-7164:
------------------------------------
I noticed you added this:
{code}
props &= ~MULTIVALUED; // must not be multivalued
{code}
But I think we should detect and throw an exception instead -- this field type
fundamentally doesn't support it. Maaaybe a warning and not an exception. But
as-is it's misconfigured in the schema.
Also, BBoxField doesn't have the "Type" suffix in its name. This issue title
and the CHANGES.txt is wrong.
> BBoxFieldType should not store values for subfields (by default)
> ----------------------------------------------------------------
>
> Key: SOLR-7164
> URL: https://issues.apache.org/jira/browse/SOLR-7164
> Project: Solr
> Issue Type: Improvement
> Components: spatial
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-7164-bbox-stored.patch
>
>
> When the bbox field creates the subfields, it uses the schema for 'double'
> and 'boolean' types.
> As is, we can specify these field types as indexed, not stored -- but that is
> a bit trappy.
> Lets add a property to the field definition:
> {code}
> storeSubFields="false"
> {code}
> and register the subfields appropriatly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
