[
https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616762#action_12616762
]
Noble Paul commented on SOLR-139:
---------------------------------
* If your index is really big most likely you may have a master/slave
deployment. In that case only master needs to store the data copy. The slaves
do not have to pay the 'update tax'
bq. Perhaps we want to write the xml to disk when it is indexed, then reload it
when the file is 'updated', perhaps the content should be stored in a SQL db.
Writing the xml may not be an option if I use DIH for indexing (there is no
xml). And what if I use CSV. That means multiple storage formats. RDDBMS
storage is a problem because of incompatibility of Lecene/RDBMS data
structures. Creating a schema will be extremely hard because of dynamic fields
I guess we can have multiple solutions. I can provide a simple
DuplicateIndexUpdateProcessor (for lack of a better name) which can store all
the data in a duplicate index. Let the user decide what he wants
bq.It's possible to recover unstored fields, if the purpose of such recovery is
to make a copy of the document and update other fields.
It is not wise to invest our time to do 'very clever' things because it is
error prone. Unless Lucene gives us a clean API to do so
> Support updateable/modifiable documents
> ---------------------------------------
>
> Key: SOLR-139
> URL: https://issues.apache.org/jira/browse/SOLR-139
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Attachments: Eriks-ModifiableDocument.patch,
> Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.patch,
> Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.patch,
> Eriks-ModifiableDocument.patch, getStoredFields.patch, getStoredFields.patch,
> getStoredFields.patch, getStoredFields.patch, getStoredFields.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-IndexDocumentCommand.patch, SOLR-139-ModifyInputDocuments.patch,
> SOLR-139-ModifyInputDocuments.patch, SOLR-139-ModifyInputDocuments.patch,
> SOLR-139-ModifyInputDocuments.patch, SOLR-139-XmlUpdater.patch,
> SOLR-269+139-ModifiableDocumentUpdateProcessor.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.
