[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470061
]
Yonik Seeley commented on SOLR-139:
-----------------------------------
Haven't had a chance to check out any code, but a few quick comments:
If the field modes were parameters, they could be reused for other update
handlers like SQL or CSV
Perhaps something like:
/update/xml?modify=true&f.price.mode=increment,f.features.mode=append
> sku=REMOVE is required because sku is a stored field that is written to with
> copyField.
I'm not sure I quite grok what REMOVE means yet, and how it fixes the copyField
problem.
Another way to work around copyField is to only collect stored fields that
aren't copyField targets. Then you run the copyField logic while indexing the
document again (as you should anyway).
I think I'll have a tagging usecase that requires removing a specific field
value from a multivalued field. Removing based on a regex might be nice too.
though.
f.tag.mode=remove
f.tag.mode=removeMatching or removeRegex
> Support updateable/modifiable documents
> ---------------------------------------
>
> Key: SOLR-139
> URL: https://issues.apache.org/jira/browse/SOLR-139
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Ryan McKinley
> Attachments: SOLR-139-IndexDocumentCommand.patch,
> SOLR-139-IndexDocumentCommand.patch, SOLR-139-XmlUpdater.patch
>
>
> It would be nice to be able to update some fields on a document without
> having to insert the entire document.
> Given the way lucene is structured, (for now) one can only modify stored
> fields.
> While we are at it, we can support incrementing an existing value - I think
> this only makes sense for numbers.
> for background, see:
> http://www.nabble.com/loading-many-documents-by-ID-tf3145666.html#a8722293
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
