[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509622
]
Yonik Seeley commented on SOLR-139:
-----------------------------------
> So you are suggesting [...]
I don't have a concrete implementation idea, I'm just going over all the things
I know people will want to do (and many of these I have an immediate use for).
> Do you mean as input or output?
Input, for index-only fields. Normally field values need to be stored for an
"update" to work, but we could also allow the user to get these field values
from an external source.
> we would need a hook at the end.
Yes, it might make sense to have more than one callback method per
UpdateRequestProcessor
Of course now that I finally look at the code, UpdateRequestProcessor isn't
quite what I expected.
I was originally thinking more along the lines of DocumentMutator(s) that
manipulate a document, not that actually initiate the add/delete/udpate calls.
But there is a certain greater power to what you are exposing/allowing too (as
long as you don't need multiple of them).
In UpdateRequestProcessor , instead of
protected final NamedList<Object> response;
Why not just expose SolrQueryRequest, SolrQueryResponse?
> 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
> Assignee: Ryan McKinley
> Attachments: SOLR-139-IndexDocumentCommand.patch,
> SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch,
> SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch,
> SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch,
> SOLR-139-IndexDocumentCommand.patch, SOLR-139-IndexDocumentCommand.patch,
> 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.
