You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
knovichikhin7 hours ago
Just an FYI, the problem with monomorphicBulkWrite and, I presume, with this one is that it's not possible to tell what statement did not execute. The reason for that is the thrown exception includes only failed items and not all items. If it were to return all items with OK/Failure status then it's possible to retry on failed items. But these response items have to match by either index or some kind of key.
@knovichikhin7 hours ago
It's more of an underlying problem. It's possible to work around this for inserts. It's harder for updates because updates are not idempotent (due to list append).
tachyonics7 hours ago
I did see that but it made sense to keep the same behaviour as monomorphicBulkWrite. We should address it in the next major version. I will create an issue for this.
The text was updated successfully, but these errors were encountered:
Context-
knovichikhin 7 hours ago
Just an FYI, the problem with
monomorphicBulkWrite
and, I presume, with this one is that it's not possible to tell what statement did not execute. The reason for that is the thrown exception includes only failed items and not all items. If it were to return all items with OK/Failure status then it's possible to retry on failed items. But these response items have to match by either index or some kind of key.@knovichikhin 7 hours ago
It's more of an underlying problem. It's possible to work around this for inserts. It's harder for updates because updates are not idempotent (due to list append).
tachyonics 7 hours ago
I did see that but it made sense to keep the same behaviour as
monomorphicBulkWrite
. We should address it in the next major version. I will create an issue for this.The text was updated successfully, but these errors were encountered: