[FEA] Add duration column types

[harrism]

Is your feature request related to a problem? Please describe.
To support arithmetic on timestamps, we need duration types.
We need to support difference between every resolution of timestamp i.e. days, seconds, milliseconds, microseconds and nanoseconds.

Describe the solution you'd like
It should be based on std::chrono::duration in libcu++.

See also #4074

• add duration types ([REVIEW] duration types #5359 [REVIEW] duration type unary casts and binary ops #5394)
• factories ([REVIEW] duration types #5359 [REVIEW] duration type unary casts and binary ops #5394)
• binary and unary operators support ([REVIEW] duration type unary casts and binary ops #5394)
• aggregation support
  • mean, sum, product - add for duration types, disable for timestamps ([REVIEW] disallow SUM and MEAN of timestamp types #5319)
    • device operators (sum, product)
    • column reduction,
    • rolling, grouped_rolling ([REVIEW] rolling support for durations types #5419)
    • groupby-aggregations ([REVIEW] durations type groupby support #5789)
• duration string support (parsing, to_string) ([REVIEW] string conversion for duration types (to_durations, from_durations) #5625)
• unary casts ([REVIEW] duration type unary casts and binary ops #5394)
• cuIO area ([REVIEW] duration - parquet read, write support #5903 [REVIEW] duration csv writer, reader support #6076 [REVIEW] fix warning unreachable code in datetime.cuh #6281)
• typed tests to include the new types ([REVIEW] rolling support for durations types #5419)
• prevent construction of timestamps with integers and force construction of timestamps with duration ([REVIEW] allow timestamps to be constructed only from duration #5735)
• support spark sql add_months api ([REVIEW] Add support for add_calendrical_months  #5931)

[devavret]

It's possible I missed a discussion regarding this.

But, just to clarify, does this need one duration type or multiple? (duration_s, duration_ms, duration_ms, duration_ns). Asking because duration_ns would be required to support differences involving timestamp_ns but wouldn't be able to represent the full range of differences between two timestamp_s.

[jrhemstad]

does this need one duration type or multiple?

Unfortunately, multiple. I believe we need a duration type for every resolution of timestamp.

[devavret]

does this need one duration type or multiple?

Unfortunately, multiple. I believe we need a duration type for every resolution of timestamp.

Ok, I'll reword the issue

[kkraus14]

Bumping this to 0.16 as the cuIO piece will not land in 0.15.

[karthikeyann]

parquet support for duration (#5903) is already done. ORC does not support duration (INTERVAL) type.
duration support for JSON and CSV only is pending in cuIO.

[karthikeyann]

All features for duration type are complete.