[
https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981177#comment-13981177
]
Kingston Duffie commented on SOLR-6003:
---------------------------------------
Shawn, your comment seems inconsistent to me. You say, "you are reading it
correctly", which tells me that you agree that ALL indexed fields must be
stored even if you are only updating one specific field that is stored.
However you go on to say that, "... it would not be a problem for that
field to be unstored" (as long as the action is "set").
Again, I'm feeling like I may just be missing something. It makes perfect
sense to me that field updates to stored fields should not cause a problem
even if other indexed fields are not stored. However, that's not what the
documentation says. It says, (and I quote):
"The core functionality of atomically updating a document requires that all
fields in your SchemaXml <https://wiki.apache.org/solr/SchemaXml> must be
configured as stored="true" except for fields which are <copyField/>
destinations
-- which must be configured as stored="false". This is because the atomic
updates are applied to the document represented by the existing stored
field values."
I assumed that this meant that after the update is applied, the full
document is reindexed and if indexable fields are not all present at that
time, then that information will be lost in the index.
This whole bug is premised on this assumption of mine -- i.e., that it is
trivial to unambiguously detect this situation and report an error. But if
this assumption is incorrect, I will be delighted -- because in my case I
have one small field that needs to be updated, while I would strongly
prefer not to have to store other large fields that I index. (Think about
changing tags associated with large documents where the body of the
document will never change, but tags associated with the document will be
updated later. I'd rather not store the document body.)
> 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]
