Fork me on GitHub
#onyx
<
2018-03-27
>
sparkofreason14:03:00

What is the lifetime of aggregation (or other) state associated with windows?

michaeldrogalis15:03:58

@dave.dixon Permanent until removed via eviction with a trigger.

sparkofreason15:03:00

Thanks. On implementation: are they all stored in memory, or in there a mechanism to swap in/out?

michaeldrogalis15:03:56

Stored in memory temporarily, durably checkpointed to S3 for fault recovery. There's an incremental version to keep only some state in memory.

sparkofreason15:03:45

Very cool, if I understand correctly, and is going on make my life really easy. Our system is being built around aggregating events over time windows for things like dashboard charts. with commands to retrieve the state for a given window. Sounds I should be able to keep that stuff for an extended time without filling up peer memory. Any other issues I might need to consider?

dbernal15:03:32

Is partitioning by multiple columns supported on onyx-sql yet? I'm referencing this issue https://github.com/onyx-platform/onyx-sql/issues/8 that says there was some work completed but it seems like it was around UUIDs. There's also another open issue https://github.com/onyx-platform/onyx-sql/issues/25 that says that partitioning by UUID is broken since 0.10.0 . Anyone know the current status of sql partitioning?