On 2022-12-23 3:28 AM, Thomas Corthals wrote:
Hi Dima,
If your schema is configured correctly for atomic updates, you can add
child documents atomically as well.
My reading of TFM is that atomic updates require all fields to be either
stored or docValues = true and that is not the case with the default
definition of _root_ and _nest_path_.
Furthermore in the default schema _text_ is defined as neither stored
not docValues = true, but the copyField directive for it is commented
out "because it's very expensive to index everything twice". (That's
probably a bug: the field definition should be inside the commented-out
bit too.)
I.e. the schema created by default is not suitable for atomic updates,
is that correct? (Yet the update commands seem to work fine with "flat"
documents anyway.)
Thx
Dima
