[
https://issues.apache.org/jira/browse/FLINK-34500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SuDewei updated FLINK-34500:
----------------------------
Description:
This issue aims to verify
[FLIP-367|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263429150].
Volunteers can verify it by following the [doc
changes|https://github.com/apache/flink/pull/24234]. Since currently only the
pre-defined DataGen connector and user-defined connector supports setting
source parallelism, volunteers can verify it through DataGen Connector.
The basic steps include:
1. Start a Flink cluster and submit a Flink SQL Job to the cluster.
2. In this Flink Job, use the DataGen SQL Connector to generate data.
3. Specify the parameter scan.parallelism in DataGen connector options as
user-defined parallelism instead of default parallelism.
4. Observe whether the parallelism of the source has changed on the job graph
of the Flink Application UI, and whether the shuffle mode is correct.
If everything is normal, you will see that the parallelism of the source
operator is indeed different from that of downstream, and the shuffle mode is
rebalanced by default.
was:
This issue aims to verify
[FLIP-367|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263429150].
Volunteers can verify it by following the [doc
changes|https://github.com/apache/flink/pull/24234]. Since currently only the
pre-defined DataGen connector and user-defined connector supports setting
source parallelism, volunteers can verify it through DataGen Connector. The
basic steps include:
1. Start a Flink cluster and submit a Flink SQL Job to the cluster.
2. In this Flink Job, use the DataGen SQL Connector to generate data.
3. Specify the parameter scan.parallelism in DataGen connector options as
user-defined parallelism instead of default parallelism.
4. Observe whether the parallelism of the source has changed on the job graph
of the Flink Application UI, and whether the shuffle mode is correct.
If everything is normal, you will see that the parallelism of the source
operator is indeed different from that of downstream, and the shuffle mode is
rebalanced by default.
> Release Testing: Verify FLINK-33261 Support Setting Parallelism for Table/SQL
> Sources
> -------------------------------------------------------------------------------------
>
> Key: FLINK-34500
> URL: https://issues.apache.org/jira/browse/FLINK-34500
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Parent, Table SQL / API
> Affects Versions: 1.19.0
> Reporter: SuDewei
> Priority: Blocker
> Fix For: 1.19.0
>
>
> This issue aims to verify
> [FLIP-367|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263429150].
> Volunteers can verify it by following the [doc
> changes|https://github.com/apache/flink/pull/24234]. Since currently only the
> pre-defined DataGen connector and user-defined connector supports setting
> source parallelism, volunteers can verify it through DataGen Connector.
> The basic steps include:
> 1. Start a Flink cluster and submit a Flink SQL Job to the cluster.
> 2. In this Flink Job, use the DataGen SQL Connector to generate data.
> 3. Specify the parameter scan.parallelism in DataGen connector options as
> user-defined parallelism instead of default parallelism.
> 4. Observe whether the parallelism of the source has changed on the job graph
> of the Flink Application UI, and whether the shuffle mode is correct.
> If everything is normal, you will see that the parallelism of the source
> operator is indeed different from that of downstream, and the shuffle mode is
> rebalanced by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
