Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".
Discussion thread | https://lists.apache.org/thread/xxx4k1qx6lodhbkknkhjyl0lq9bx8fcpjvn | ||||||||
---|---|---|---|---|---|---|---|---|---|
Vote thread | https://lists.apache.org/thread/lktnb162l2z3042m76to6xfbsdndy4r7 | ||||||||
JIRA |
| ||||||||
Release | 1.20 |
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
In addition, the current configuration option `table.exec.hive.infer-source-parallelism` acts not only as a switch to enable or disable hive source parallelism inference but also as a prefix for other configuration options (e.g. `table.exec.hive.infer-source-parallelism.max`). This practice does not conform to the standards of YAML specifications. Besides, with the introduction of `table.exec.hive.infer-source-parallelism.mode`
, we can disable parallelism inference by specifying InferMode.NONE, thus substituting the function of `table.exec.hive.infer-source-parallelism`
. Therefore, we plan to mark `table.exec.hive.infer-source-parallelism`
as Deprecated in this FLIP. Before this configuration option is completely phased out, `table.exec.hive.infer-source-parallelism`
will still serve as the main switch to enable or disable parallelism inference.
The temporary coexistence logic of the two configuration options is as follows:
Inference Mode Relationship Table | |||
---|---|---|---|
`table.exec.hive.infer-source-parallelism` | `table.exec.hive.infer-source-parallelism.mode` | ||
DYNAMIC | STATIC | NONE | |
true | dynamic parallelsim inference | static parallelism inference | disabled |
false | disabled | disabled | disabled |
Behavior Change
After introducing this FLIP, the behavior changes are as follows:
...