You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "devinjdangelo (via GitHub)" <gi...@apache.org> on 2023/08/29 13:01:28 UTC
[GitHub] [arrow-datafusion] devinjdangelo opened a new issue, #7442: Allow Setting Column Specific Parquet Write Options via SQL StatementOptions
devinjdangelo opened a new issue, #7442:
URL: https://github.com/apache/arrow-datafusion/issues/7442
### Is your feature request related to a problem or challenge?
Currently StatementOptions only enables setting parquet writer options for all columns at once (the default value). In many cases, we would want to set column level encodings or other settings based on the data type and properties of that specific column.
### Describe the solution you'd like
Implement a syntax to allow specifying column level parquet settings. A possible syntax for this would be:
```sql
COPY my_table
TO ./path
(format parquet,
encoding_default plain,
encoding '(colA RLE, nested.col.path.colB dictionary, ...)',
)
```
### Describe alternatives you've considered
DuckDB supports a different syntax than described above for setting field_id for each column. See https://duckdb.org/docs/sql/statements/copy.html
### Additional context
_No response_
--
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: github-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] parkma99 commented on issue #7442: Allow Setting Column Specific Parquet Write Options via SQL StatementOptions
Posted by "parkma99 (via GitHub)" <gi...@apache.org>.
parkma99 commented on issue #7442:
URL: https://github.com/apache/arrow-datafusion/issues/7442#issuecomment-1697534645
https://github.com/apache/arrow-datafusion/blob/85ec31433615735a05d332f87cd0bdfc11aac663/datafusion/core/src/physical_planner.rs#L555-L598
May be we can get `output_schema` by using table origin schema and `statement_options`!
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb closed issue #7442: Allow Setting Column Specific Parquet Write Options via SQL StatementOptions
Posted by "alamb (via GitHub)" <gi...@apache.org>.
alamb closed issue #7442: Allow Setting Column Specific Parquet Write Options via SQL StatementOptions
URL: https://github.com/apache/arrow-datafusion/issues/7442
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org