[ 
https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980496#comment-13980496
 ] 

Kingston Duffie commented on SOLR-6003:
---------------------------------------

I agree.  Our ultimate goal, of course, is just to remove the restriction that 
all non-copied fields must be stored if you want to use field updates on any 
field.  Until we get there, the spirit of SOLR-6003 is simply to report an 
error to those systems that may try to use field updates on a schema that can't 
support it.  

My own experience was that since I was unaware of this rather obscure 
restriction, we thought field updates were working just fine.  Only later did 
we discover that certain queries (but not all!) were failing to find documents 
based on certain fields.  I thought if there were a simple change that detected 
the situation and produced an error, the next guy wouldn't have to suffer as I 
did.  Admittedly, "read the documentation" is a reasonable answer.  I wish I 
had.

> 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

Reply via email to