-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Is your feature request related to a problem or challenge?
Before #9382, DataFusion write configuration was inconsistent and different than the main configuration system and #9382 rationalized it ❤️
However, it also broke compatibility with old configuration and introduced some redundancy that can be annoying, as @devinjdangelo noted #9382 (review)
For example, to specify the compression type when writing parquet, after #9382 one needs to repeat 'parquet' to namespace the configuration options (format parquet and 'parquet.compression')
DataFusion CLI v36.0.0
❯ COPY (values (1)) TO 'test_files/scratch/copy/table/' (format parquet, 'compression' 'zstd(10)');
Invalid or Unsupported Configuration: could not find config namespace for key "compression"
❯ COPY (values (1)) TO 'test_files/scratch/copy/table/' (format parquet, 'parquet.compression' 'zstd(10)');
+-------+
| count |
+-------+
| 1 |
+-------+
1 row in set. Query took 0.024 seconds.Describe the solution you'd like
I would like to introduce some backwards compatibility so when I write
COPY source_table TO 'test_files/scratch/copy/table/' (format parquet, 'compression' 'zstd(10)');It means the same as
COPY source_table TO 'test_files/scratch/copy/table/' (format parquet, 'parquet.compression' 'zstd(10)');Describe alternatives you've considered
I suggest we add some sort of special case code that tried to parse the option as normal, and if that failed, try with the different formats / prefixes
For example, if compression wasn't a valid option,
Additional context
No response