[
https://issues.apache.org/jira/browse/SOLR-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-7164:
--------------------------------
Attachment: SOLR-7164-bbox-stored.patch
here is a patch
the use case is to make users be explicit about wanting to store the sub
fields. If you do store the fields, weird things happen with the 'update'
feature -- since it treats them as explicitly set values.
As is, you can avoid this by creating a special field type that is not stored.
but i think most users (at least most schemas I have seen) set the
indexed/stored properties on fields, not field types
> 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
> 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]
