Can you confirm that your Solr schema satisfies this stated requirement from
the description you referenced:
"If there's a field in the Solr schema that's not stored=True, it will get
dropped from documents in Solr on the next update to that document. Indexing
won't fail, but that field simply won't have any content any more."
IOW, the stored="true" attribute is needed on any Solr fields that you wish
to preserve on atomic update operations.
-- Jack Krupansky
-----Original Message-----
From: mohit2360
Sent: Thursday, February 6, 2014 6:44 AM
To: [email protected]
Subject: Retrieving the document after partial updates.
I have made all the suggested changes to my project so far suggested through
various forum.
like :: http://plone.org/products/ftw.solr
Though the fields are partially updated but when is projection is selected
it shows only the fields used in the app for updates and "_version_" with
some value but not the all the fields of the document.
Scenario :::
these many fields in the documents
[{"person_id":203433,"fname":"Amar","lname":"Jyadav","isLoggedIn":true}]
after setting ,"isLoggedIn" to false then to its showing then to it is not
showing any changes but rather this is projected by Solr engine.
[{"person_id":203433,"isLoggedIn":true,"_version_":1459287359397822464}]
rest fields like fname, lname are not there after partial updates.
Solution required as soon as possible.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Retrieving-the-document-after-partial-updates-tp4115808.html
Sent from the Lucene - Java Developer mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
