Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[C++, Python] Allow specifying column names to CSV reader #21421

Closed
asfimport opened this issue Mar 16, 2019 · 2 comments
Closed

[C++, Python] Allow specifying column names to CSV reader #21421

asfimport opened this issue Mar 16, 2019 · 2 comments

Comments

@asfimport
Copy link

Currently I think there is no way to specify custom column names for CSV files. It's possible to specify the full schema of the file, but not just column names.

See the related discussion here: ARROW-3722

The goal of this is to re-use the CSV type-inference but still allow people to specify custom names for the columns. As far as I know, there is currently no way to set column names post-hoc, so we should provide a way to specify them before reading the file.

Related to this, ParseOptions(header_rows=0) is not currently implemented.

Is there any current way to do this or does this need to be implmented?

Reporter: Philipp Moritz / @pcmoritz
Assignee: Ben Kietzman / @bkietz

PRs and other links:

Note: This issue was originally created as ARROW-4912. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Antoine Pitrou / @pitrou:
If there's no way to change column names post-hoc, then perhaps we should just add one? That sounds more universal than adding ad hoc options to the CSV reader.

As for the header_rows=0, can you open a separate issue?

@asfimport
Copy link
Author

Francois Saint-Jacques / @fsaintjacques:
Issue resolved by pull request 4557
#4557

@asfimport asfimport added this to the 0.14.0 milestone Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants