Skip to content

Commit 77a543e

Browse files
Apply suggestion from @mirnawong1
Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
1 parent 2cd1a18 commit 77a543e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

website/snippets/_fusion-threads.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,6 @@
55
| **BigQuery** | Fusion respects user-set threads to manage API rate limits. |
66
| **Redshift** | Fusion respects user-set threads to manage concurrency limits. |
77

8-
For BigQuery and Redshift, setting `--threads 0` (or omitting the setting) allows Fusion to dynamically optimize parallelism.
8+
- For Snowflake and Databricks, <Constant name="fusion"/> manages parallelism automatically and ignores user-set thread values. The only supported override is `threads: 1`, which can also help resolve timeout issues if set.
99

1010
- For BigQuery and Redshift, <Constant name="fusion"/> respects user-set thread values to accommodate warehouse-specific limits. Setting `--threads 0` (or omitting the setting) allows <Constant name="fusion"/> to dynamically optimize parallelism.

0 commit comments

Comments
 (0)