ordered insertMany incorrectly fails if an row has pre-execution error #1672
Assignees
Labels
Comments
|
It was later clarified that if by "faulty row" one means "a row with a wrong type", then the fact that no insertions occur is by design: Tables do preemptive all-rows data validation and this is the expected behaviour. |
|
re-open as we are discussing |
amorton
added
dec-hotfix
Open
4 tasks
|
moved out of the dec-hotfix because it is not a blocking problem, and though small the change is deep and I want to make sure we get it correct. |
|
moved to To-Do because we are working on it. @Yuqi-Du I think the fix is like you have, but simplier. When the processing is sequential the only test is that we fail if the current attempt is in error state. Also, I would like to have unit tests to test the behaviour |
amorton
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symptom: insertMany on tables, when
ordered=Trueand there's a faulty row in mid-list, does not insert even those coming prior to that one.This is at odds with Collections (ordered=true), where the docs are inserted sequentially until the erroring one.
Also in that case the response has no
"status"field at all.(first reported here).
The text was updated successfully, but these errors were encountered: