[
https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981032#comment-13981032
]
Shawn Heisey commented on SOLR-6003:
------------------------------------
Hoss is right: I had not considered dynamic fields.
It should be possible to detect the *general* case of "this schema might be
unsuitable" even with dynamic fields, as [~kduffie] described in his code
example. My code example was trying to detect the *specific* case of "this
particular atomic update WILL lose data with the current schema." Because I
haven't examined the code yet, I do not know how difficult dynamic field
support will be.
Because they are *probably* easy, a combination of the general case with
dynamic fields and the specific case with explicit fields would be a good
starting point. Test cases will be required. After that's done, hopefully
dynamic fields can be fully supported in the specific case, eliminating the
need for the general case.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
