I understand you have a situation where doing the right thing causes wrong
results :) Well, if the client code is not localized to a particular
service, I would tackle it from the server side via a custom update
processor extending the UpdateRequestProcessorFactory and adding it to a
custom update
On 9/26/23 14:06, Rahul Goswami wrote:
I typically set the field value to null in an atomic update if I want to
remove the field. Eg: If a document is soft deleted via a field
"isVisible":false , then I would want to drop its "content" field by
setting it to null (since it is large and not requir
Hi Shawn,
I typically set the field value to null in an atomic update if I want to
remove the field. Eg: If a document is soft deleted via a field
"isVisible":false , then I would want to drop its "content" field by
setting it to null (since it is large and not required anymore) in an
atomic update
In SolrJ 4.7.2, if an atomic update request is sent with some fields set
to null (the object, not the string), then those fields will be ignored
when processing the atomic update -- no change.
In SolrJ 9, a field set to null in an atomic update request will be
removed from the document.
This
