[
https://issues.apache.org/jira/browse/SOLR-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337517#comment-14337517
]
Ryan McKinley commented on SOLR-7164:
-------------------------------------
bq. I'd like to better appreciate this problem – I don't understand it
are you asking about the 'update' issue? If so, i can just explain it -- my
real concern is really that I don't want to accidentally create stored fields!
with the update feature, it reads out all stored fields and then writes them
back to the index... so if you update the bbox, that would write the various
subfields as if the original request had them. I'm not sure the exact
behavior, but it seem unpredictable and will depend on field ordering etc. If
the field is multi-valued it may work, but that is also an incorrect assumption
for the normal case
> 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]
