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
Antoine Pitrou / @pitrou:
This is handled in ARROW-3722 (see pull request: #2950). You will be able to specify data types for each column, including BooleanType().
Wes McKinney / @wesm:
It wouldn't be too harmful if the default recognized T/F values are a conservative set like "true"/"false" or "TRUE"/"FALSE". We might collect data on what other projects do in this regard. I would opt for developer control, though, so this might be something we make configurable (whether type inferences tries boolean by default or not)
Kouhei Sutou / @kou:
Yes. I want type inference for boolean. Sorry for my ambiguous title.
I think that specifying type explicitly is very useful. But type inference is also useful even if it may choose wrong type because it's convenient. If type inference is failed, we can specify type explicitly. It's convenience than we specify all types explicitly.
Reporter: Kouhei Sutou / @kou
Assignee: Antoine Pitrou / @pitrou
PRs and other links:
Note: This issue was originally created as ARROW-3791. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: