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
feat!: Support table_concurrency and resource_concurrency (#268)
#### Summary
Closescloudquery/cloudquery#2313cloudquery/cloudquery#159#264
This renames `concurrency` to `table_concurrency` (this has the same behaviour as previously but the name was too generic).
Also this introduce a new option `resource_concurrency` - this limits the number of go routines that resolve a specific resource (useful when a lot of column resolvers that have api calls and `PreResourceResolver`).
Importe Note: both options are only for top-level concurrency control i.e we only spawn go-routines for parent tables and for resources of parent table. The reason for that is that there is no concurrency model that can work with one variable for recursive calls otherwise it will get deadlock.
So right now the SDK will support only for one level - in the future if we want to support additional level we can do `table_concurrency_1` and `resource_concurrency_1` but I think for now we can skip this.
0 commit comments