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
For timestamp datatypes, if the timezone parameter is non-empty, the int64 array values in the associated column are assumed to be normalized to UTC. This requirement should be made clear to the C++ API user. (It can be inferred from the flatbuffers schema, but that internal implementation document probably wouldn't ordinarily be consulted by a C++ API consumer.)
TP Boudreau / @tpboudreau:
On further review, the flatbuffers spec contains quite a bit of usage information and probably is intended to be a primary resource for developers. (Sorry for the noise.)
For timestamp datatypes, if the timezone parameter is non-empty, the int64 array values in the associated column are assumed to be normalized to UTC. This requirement should be made clear to the C++ API user. (It can be inferred from the flatbuffers schema, but that internal implementation document probably wouldn't ordinarily be consulted by a C++ API consumer.)
Reporter: TP Boudreau / @tpboudreau
Assignee: TP Boudreau / @tpboudreau
PRs and other links:
Note: This issue was originally created as ARROW-5545. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: