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
Allow the user to supply the col_names argument from readr when reading in a dataset.
This is already possible when reading in a single CSV file via arrow::read_csv_arrow() via the readr_to_csv_read_options function, and so once the C++ functionality to autogenerate column names for Datasets is implemented, we should hook up readr_to_csv_read_options in csv_file_format_read_opts just like we have with readr_to_csv_parse_options in csv_file_format_parse_options.
Nicola Crane / @thisisnic:
Is supporting logical values here actually going to be useful to users (in which case I need to open a C++ component ticket to enable autogeneration of column names for datasets), or would we be better enabling this argument, but testing the user-supplied value and if it's TRUE or FALSE, raise an error saying this isn't supported, but if it's a vector of column names just pass it through to the equivalent parameter (i.e. column_names)?
Allow the user to supply the
col_names
argument fromreadr
when reading in a dataset.This is already possible when reading in a single CSV file via
arrow::read_csv_arrow()
via thereadr_to_csv_read_options
function, and so once the C++ functionality to autogenerate column names for Datasets is implemented, we should hook upreadr_to_csv_read_options
incsv_file_format_read_opts
just like we have withreadr_to_csv_parse_options
incsv_file_format_parse_options
.Reporter: Will Jones / @wjones127
Assignee: Will Jones / @wjones127
PRs and other links:
Note: This issue was originally created as ARROW-15812. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: