As I understand it, the proposal is to have both an interval data type[1] and a
timedelta type[2]. The interval is compatible with the SQL standard (but not
Postgres) and can be implemented with a single numeric value representing a
particular time unit (year, month, day, hour, minute, second,
Wes McKinney created ARROW-1768:
---
Summary: [Python] Fix suppressed exception in ParquetWriter.__del__
Key: ARROW-1768
URL: https://issues.apache.org/jira/browse/ARROW-1768
Project: Apache Arrow
Wes McKinney created ARROW-1767:
---
Summary: [C++] Supports file reads and writes over 2GB on Windows
Key: ARROW-1767
URL: https://issues.apache.org/jira/browse/ARROW-1767
Project: Apache Arrow
I
It seems like we don't have enough input on this topic to make a
decision right now. I placed the JIRA ARROW-352 in the 0.9.0
milestone, but we really should try to get this done soon so that
downstream users are not blocked on using Arrow to send around
interval data.
- Wes
On Fri, Oct 20, 2017
