Well, it is known to me and documented in my book. BTW, that field value is
simply ignored.
There are tons of places in Solr where undefined values or outright garbage
are simply ignored, silently.
Go ahead and file a Jira though.
-- Jack Krupansky
-----Original Message-----
From: Sam Antique
Sent: Friday, June 28, 2013 6:12 PM
To: solr-user@lucene.apache.org
Subject: An issue with atomic updates?
Hi all,
I think I have found an issue (or misleading behavior, per say) about
atomic updates.
If I do atomic updates on a field, and if the operation is none-sense
(anything other than add, set, inc), it still returns success. Say I send:
/update/json?commit=true -d '[{"id":"...", "field1":{"add":"value"}}]'
it adds fine and return success. But if I continue:
/update/json?commit=true -d '[{"id":"...",
"field1":{"none-sense":"value"}}]'
It still returns status:0, which is a bit misleading.
Is this a known issue?
Thanks,
Sam
