[
https://issues.apache.org/jira/browse/FLINK-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-8236:
----------------------------------
Labels: auto-deprioritized-major stale-major (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Allow to set the parallelism of table queries
> ---------------------------------------------
>
> Key: FLINK-8236
> URL: https://issues.apache.org/jira/browse/FLINK-8236
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 1.4.0
> Reporter: Timo Walther
> Priority: Major
> Labels: auto-deprioritized-major, stale-major
>
> Right now the parallelism of a table program is determined by the parallelism
> of the stream/batch environment. E.g., by default, tumbling window operators
> use the default parallelism of the environment. Simple project and select
> operations have the same parallelism as the inputs they are applied on.
> While we cannot change forwarding operations because this would change the
> results when using retractions, it should be possible to change the
> parallelism for operators after shuffling operations.
> It should be possible to specify the default parallelism of a table program
> in the {{TableConfig}} and/or {{QueryConfig}}. The configuration per query
> has higher precedence that the configuration per table environment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
