We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should the batch query jobs i.e. SELECT follow this parallelism? Do you mean default parallelism of the non-scan stages? Good catch. 🤔 Yes, exactly.
Should the batch query jobs i.e. SELECT follow this parallelism? Do you mean default parallelism of the non-scan stages? Good catch. 🤔
Should the batch query jobs i.e. SELECT follow this parallelism?
SELECT
Do you mean default parallelism of the non-scan stages? Good catch. 🤔
Yes, exactly.
Maybe we need another BATCH_PARALLELISM for this. 😄
BATCH_PARALLELISM
Originally posted by @BugenZhao in #7370 (comment)
Currently, the parallelism of each stage in distributed batch query is determined as follows:
Sometimes users may want to increase the number of parallelism stages, and we can have a session variable batch_parallelism for this.
batch_parallelism
The text was updated successfully, but these errors were encountered:
closed by #8552
Sorry, something went wrong.
liurenjie1024
ZENOTME
No branches or pull requests
Maybe we need another
BATCH_PARALLELISM
for this. 😄Originally posted by @BugenZhao in #7370 (comment)
Currently, the parallelism of each stage in distributed batch query is determined as follows:
Sometimes users may want to increase the number of parallelism stages, and we can have a session variable
batch_parallelism
for this.The text was updated successfully, but these errors were encountered: