Optional `groupObjects` argument in bulk operations mutations that offers faster and more reliable job execution

Changelog
1

We've introduced a new groupObjects argument to bulkOperationRunQuery and bulkOperationRunMutation mutations in the GraphQL Admin API that allow clients optionally to disable grouping and benefit from faster and more reliable bulk operation job runs.

This is a companion discussion topic for the original entry at https://shopify.dev/changelog/optional-groupobjects-argument-in-bulk-operations-mutations-that-offers-faster-and-more-reliable-job-execution
2

Will this still ensure child objects are always somewhere below the parent object? Even if not directly below like before?

1 Like
4

Hey David,

Great question. I checked here and it is reasonable to assume that they will be somewhere below the parent object and what is most likely to be what happens, however do to the async nature of the bulk queries with grouping disabled, we can’t guarantee that it will always happen that way.

5

Hi @KyleG-Shopify,

However, the same assumption is confirmed by @Liam-Shopify here:

Then… what is the final answer?

6

Hey Francisco,

Happy to clarify. We would expect the children to always be after the parents. If you see an edge case where that doesn’t happen, let us know.

With that in mind, if you’re relying on a specific order, I’d recommend leaving grouping enabled.

Hope that helps.

1 Like