>
> Looking more at the Postgres spec and storage details, I'd be
> supportive of having a COMPLEX interval type which could be a packed
> type (possibly using the same 16-byte storage layout as Postgres --
> depending on whether this complex interval needs granularity smaller
> than seconds, more
Looking more at the Postgres spec and storage details, I'd be
supportive of having a COMPLEX interval type which could be a packed
type (possibly using the same 16-byte storage layout as Postgres --
depending on whether this complex interval needs granularity smaller
than seconds, more analysis nee
Indeed, I did, with both serde json and dynamodb. Inside an arrow schema,
the metadata field is a hashmap with skip serializing if empty. When
deserializing, it expects a metadata field. I would expect that every
schema can be serialized-deserialized back in itself.
Jack
On Sat, Apr 3, 2021, 10:5
Arrow Build Report for Job nightly-2021-04-04-0
All tasks:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-04-04-0
Failed Tasks:
- conda-linux-gcc-py37-aarch64:
URL:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-04-04-0-drone-conda-linux
