[
https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976359#comment-13976359
]
Erick Erickson commented on SOLR-6003:
--------------------------------------
I see what you're asking, but I'm not at all clear that it's a good idea. It's
perfectly reasonable to have fields that are _not_ stored and still use atomic
updates, consider copyField directives for instance. There's no need to store
the destination fields for atomic updates to work fine.
You'd need to have conditions like, "Return an error if any field is not stored
_and_ it's not the destination of a stored field that's a copyField", which
starts to get very error-prone.
There's work being done on updates that do not require fields to be stored,
but I don't know how that's going....
> JSON Update increment field with non-stored fields causes subtle problems
> -------------------------------------------------------------------------
>
> Key: SOLR-6003
> URL: https://issues.apache.org/jira/browse/SOLR-6003
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 4.7.1
> Reporter: Kingston Duffie
>
> In our application we have large multi-field documents. We occasionally need
> to increment one of the numeric fields or add a value to a multi-value text
> field. This appears to work correctly using JSON update. But later we
> discovered that documents were disappearing from search results and
> eventually found the documentation that indicates that to use field
> modification you must store all fields of the document.
> Perhaps you will argue that you need to impose this restriction -- which I
> would hope could be overcome because of the cost of us having to store all
> fields. But in any case, it would be better for others if you could return
> an error if someone tries to update a field on documents with non-stored
> fields.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
