News for hackers. Stuff that matters.

A comment on Building columnar compression in a row-oriented database. Parent comment

Re:Building columnar compression in a row-oriented database by jnordwick on Thursday October 31, 2019 @05:02PM (#21413682)
Sounds like he's describing a bitemporal database (although not in the canonical form usually associated with them).

I've looked into timescaledb for this, and it doesn't support them.

[ Parent | on HN ]
Re:Building columnar compression in a row-oriented database by refset on Thursday October 31, 2019 @05:42PM (#21414007)
I agree. Bitemporal databases can natively handle late-arriving data in these kinds of upstream timestamp integration scenarios.

However, the intersection of bitemporal indexes and columnar time-series queries seems important and yet I haven't seen anything that looks like it might offer both, possibly asides from kdb+ and SAP HANA.

Disclosure: I work on https://github.com/juxt/crux (which is optimised for bitemporal graph joins and doesn't currently employ columnar indexes)

[ Parent | on HN ]