for bulk operations, don't raise an exception if any of the ingested items fails

[philvarner]

Related Issue(s):

• n/a

Description:

The default behavior of the bulk api (which streams the individual operations in batches) is to immediately stop and raise an exception if any of the operations in a batch fail. Instead, don't raise on that error, and just keep ingesting the items. This is so that if there's a bad item that's being ingested, it doesn't prevent the others in the batch from being ingested.

TBD is better reporting back to the caller as to which items succeeded and failed.

PR Checklist:

• Code is formatted and linted (run pre-commit run --all-files)
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
• Changes are added to the changelog

[gadomski]

Is it worth making this an optional argument to bulk_async in case someone else wants different behavior?

[philvarner]

Is it worth making this an optional argument to bulk_async in case someone else wants different behavior?

Yes, but not as part of this work -- right now, it's just blowing up because the exception is getting thrown, but there should really be a more formalized response as part of the Transactions spec, similarly to how ES handles it by returning a result for each document that's indexed.