[ 
https://issues.apache.org/jira/browse/FLINK-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex updated FLINK-13441:
-------------------------
    Description: 
We should adapt the existing batch E2E test to use the newly introduced 
{{ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}} and verify that the 
job runs on a cluster with fewer slots than the job's parallelism. In order to 
make this work, we need to set the shuffles to be blocking via 
{{ExecutionMode#BATCH}}. As a batch job we should use the 
{{DataSetAllroundTestProgram}}.

 *Update:* currently, the 
{{ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}} option is set only 
by table planner(s) and cannot be set (configured) for general purpose (batch) 
job. As agreed offline, this ticket would add a new e2e test for batch sql job 
instead of modifying {{DataSetAllroundTestProgram}}.

 

  was:We should adapt the existing batch E2E test to use the newly introduced 
{{ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}} and verify that the 
job runs on a cluster with fewer slots than the job's parallelism. In order to 
make this work, we need to set the shuffles to be blocking via 
{{ExecutionMode#BATCH}}. As a batch job we should use the 
{{DataSetAllroundTestProgram}}.


> Add batch E2E test which runs with fewer slots than parallelism
> ---------------------------------------------------------------
>
>                 Key: FLINK-13441
>                 URL: https://issues.apache.org/jira/browse/FLINK-13441
>             Project: Flink
>          Issue Type: Test
>          Components: API / DataSet, Tests
>            Reporter: Till Rohrmann
>            Assignee: Alex
>            Priority: Blocker
>             Fix For: 1.9.0
>
>
> We should adapt the existing batch E2E test to use the newly introduced 
> {{ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}} and verify that 
> the job runs on a cluster with fewer slots than the job's parallelism. In 
> order to make this work, we need to set the shuffles to be blocking via 
> {{ExecutionMode#BATCH}}. As a batch job we should use the 
> {{DataSetAllroundTestProgram}}.
>  *Update:* currently, the 
> {{ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST}} option is set only 
> by table planner(s) and cannot be set (configured) for general purpose 
> (batch) job. As agreed offline, this ticket would add a new e2e test for 
> batch sql job instead of modifying {{DataSetAllroundTestProgram}}.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to