Currently it changes the database but not the object used
as a parameter. Since both are not synced, the next call
will re-trigger a database update even if there was no need
for it.
In elasticsearch also fetch the document only when we really
need, else we end up doing one synchronous query each time
we write a point.
Coverage increased (+0.007%) to 81.93% when pulling 7194012a07ede367f431db39bc9b8751c1fe2c28 on iksaif:fix-updated-on into ee307c7f6deb233dcc8cc0d94a2620f048c53822 on criteo:master.
Currently it changes the database but not the object used as a parameter. Since both are not synced, the next call will re-trigger a database update even if there was no need for it.
In elasticsearch also fetch the document only when we really need, else we end up doing one synchronous query each time we write a point.