What’s changing
We’ve updated our pre-aggregations set-up to support more functionality: partitioning, incremental, and refreshKeys that you can use in your model.
Can I use refresh keys directly in the model?
Yes. You can pass a time period (e.g. “x hours”), an SQL parameter like SELECT MAX(created_at) FROM orders, or a cron schedule (e.g. “refresh at 8 AM”).
Here’s what your model and pre-aggregation looks like before and after the change:
Do I still need to provide security contexts via the caching API?
Yes - you’ll provide these via the caching API - Cube docs here. However the refreshInterval isn’t needed anymore.
Here’s what your caching api request looks like before and after the change:
Is there still a limit on security contexts?
No. The old limit of 30 has been removed.
Do I need to pass timezones?
If your client requires a timezone, it must still be passed via the caching API.
We will be updating our main docs page shortly - bear with us 