lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kingston Duffie (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems
Date Fri, 25 Apr 2014 14:44:19 GMT

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

Kingston Duffie edited comment on SOLR-6003 at 4/25/14 2:44 PM:
----------------------------------------------------------------

Erick,  I was referring to the section on Stored Values in Caveats and Limitations on this
page:  [https://wiki.apache.org/solr/Atomic_Updates]  where it says that ALL non-copy fields
must be stored.  But perhaps I'm reading more into that than is actually required.  If it
will work to store ONLY those fields that may be updated, that would be a huge savings for
us.  I'm unfamiliar with the implementation.  Can you confirm based on your understanding
that only fields that may be updated need to be stored?  If so, it would be great to update
the documentation accordingly.


was (Author: kduffie):
@erickerickson,  I was referring to the section on Stored Values in Caveats and Limitations
on this page:  [https://wiki.apache.org/solr/Atomic_Updates]  where it says that ALL non-copy
fields must be stored.  But perhaps I'm reading more into that than is actually required.
 If it will work to store ONLY those fields that may be updated, that would be a huge savings
for us.  I'm unfamiliar with the implementation.  Can you confirm based on your understanding
that only fields that may be updated need to be stored?  If so, it would be great to update
the documentation accordingly.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message