You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shouldn't the missing bindings reported earlier in #11632 be propagated higher up here in the parquet.py module?
Passing **kwargs as is the case for write_table would do the trick I think.
I am finding myself stuck while using pandas.to_parquet with use_legacy_dataset=false and no way to set the existing_data_behavior flag to overwrite_or_ignore
Joris Van den Bossche / @jorisvandenbossche:
Indeed, we should probably ensure users can pass that keyword in write_to_dataset as well. Currently, the **kwargs are passed to the ParquetFileFormat write options (for parquet specific write options).
Shouldn't the missing bindings reported earlier in #11632 be propagated higher up here in the parquet.py module?
Passing **kwargs as is the case for
write_table
would do the trick I think.I am finding myself stuck while using pandas.to_parquet with
use_legacy_dataset=false
and no way to set theexisting_data_behavior
flag tooverwrite_or_ignore
Reporter: christophe bagot
Assignee: Alenka Frim / @AlenkaF
PRs and other links:
Note: This issue was originally created as ARROW-15757. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: