What is the problem the feature request solves?
The configuration settings have many inconsistencies.
For example, we have many different prefixes for shuffle-related configs:
spark.comet.columnar.shuffle
spark.comet.exec.shuffle
spark.comet.native.shuffle
spark.comet.shuffle
There are also differences in convention for naming within configs:
mergeRanges (Camel Case)
thread-pool (Hyphenated)
read.parallel.io (dot separated)
Renaming any of these configs will be disruptive to users. If we do rename them, I suggest we do it for the 1.0.0 release.
We could also consider introducing a capability to support the old deprecated names for some period of time.
Describe the potential solution
No response
Additional context
No response
What is the problem the feature request solves?
The configuration settings have many inconsistencies.
For example, we have many different prefixes for shuffle-related configs:
spark.comet.columnar.shufflespark.comet.exec.shufflespark.comet.native.shufflespark.comet.shuffleThere are also differences in convention for naming within configs:
mergeRanges(Camel Case)thread-pool(Hyphenated)read.parallel.io(dot separated)Renaming any of these configs will be disruptive to users. If we do rename them, I suggest we do it for the 1.0.0 release.
We could also consider introducing a capability to support the old deprecated names for some period of time.
Describe the potential solution
No response
Additional context
No response