jira at apache
May 23, 2012, 10:30 PM
Post #1 of 2
(47 views)
Permalink
|
|
[jira] [Commented] (SOLR-139) Support updateable/modifiable documents
|
|
[ https://issues.apache.org/jira/browse/SOLR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282202#comment-13282202 ]
Seshagiri Nuthalapati commented on SOLR-139:
--------------------------------------------
yonik, I see a small issue with this.
- I have added one of the example document from exampledocs folder. The schema has "price" and "price_c" (copy field from price)
1.When i add the document, it looks as follows:
<str name="id">TWINX2048-3200PRO</str>
<str name="name">CORSAIR XMS 2GB (2 x 1GB) 184-Pin DDR SDRAM Unbuffered DDR
400 (PC 3200) Dual Channel Kit System Memory - Retail
</str>
<str name="manu">Corsair Microsystems Inc.</str>
<float name="price">185.0</float>
<arr name="price_c">
<str>185,USD</str>
</arr>
2. Now I want to set price field with 100 , so I sent a json for it.
[{"id":"TWINX2048-3200PRO","price":{"set":100}}]
Now the document looks as follows:
<str name="id">TWINX2048-3200PRO</str>
<str name="name">CORSAIR XMS 2GB (2 x 1GB) 184-Pin DDR SDRAM Unbuffered DDR
400 (PC 3200) Dual Channel Kit System Memory - Retail
</str>
<str name="manu">Corsair Microsystems Inc.</str>
<float name="price">100.0</float>
<arr name="price_c">
<str>100,USD</str>
<str>185,USD</str>
</arr>
as you can see, the old price value still there in the "price_c". Is there a workaround/patch we can do for this?
> 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
> Attachments: Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.patch, Eriks-ModifiableDocument.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-139.patch, SOLR-139.patch, SOLR-269+139-ModifiableDocumentUpdateProcessor.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields.patch, getStoredFields
.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene
|
