[
https://issues.apache.org/jira/browse/ARROW-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685325#comment-16685325
]
Antoine Pitrou commented on ARROW-3722:
---------------------------------------
> We also need a way to provide column names (or even default to numbering) for
> files without a header. This topic is related, but maybe a new Jira would be
> better suited for it.
Yes, I think a separate JIRA is better.
> additional thoughts on passing ColumnBuilder instead of just a type. Ideally,
> the user would be able to implement own converters to support, let's say,
> uncommon date formats or even parse struct types at load time.
Right now most CSV APIs are internal. APIs like ColumnBuilder and Converter
expose implementation details that we don't want to set in stone. If there's
some demand we might think about an API to let people define their conversion
functions without having to depend on internal APIs.
> [C++] Allow specifying column types to CSV reader
> -------------------------------------------------
>
> Key: ARROW-3722
> URL: https://issues.apache.org/jira/browse/ARROW-3722
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 0.11.1
> Reporter: Antoine Pitrou
> Assignee: Antoine Pitrou
> Priority: Major
>
> I'm not sure how to expose this. The easiest, implementation-wise, would be
> to allow passing a {{Schema}} (for example inside the {{ConvertOptions}}).
> Another possibility is to allow specifying the default types for type
> inference. For example type inference currently infers integers as {{int64}},
> but the user might prefer {{int32}}.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
