xiangqiao123 opened a new pull request #17826:
URL: https://github.com/apache/flink/pull/17826


   ## What is the purpose of the change
   Currently, when I disable hive table source parallelism inference using 
configuration  and set parallelism.default: 100. 
   `table.exec.hive.infer-source-parallelism: false `
   `parallelism.default: 100`
   The result is that the parallelism of hive table source is 1, and the 
configuration of the default parallelism is not effective.
   
   I will optimize this problem. In the future, when disable hive table source 
parallelism inference ,the  parallelism of hive table source will be determined 
according to the following order:
    
   1. If `table.exec.resource.default-parallelism` is set, the configured value 
will be used
   
   2. If `parallelism.default` is set, the configured value is used
   
   3. If the above two configuration items are not set, the default value is 1
   
   ## Brief change log
   
     - `HiveParallelismInference#limit` return parallelism directly when hive 
table source parallelism inference is disabled
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - Added integration tests for hive table source parallelism inference is 
disabled and set parallelism through configuration.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no 
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to