-
Notifications
You must be signed in to change notification settings - Fork 1.9k
docs: Calendar cubes #9791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Calendar cubes #9791
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻 Nice work!
I left some typos and questions that I hope you'll find useful.
| # ... | ||
| </CodeTabs> | ||
|
|
||
| #### `time_dimension` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about a named time shift specification?
| type: count | ||
| public: false | ||
| ``` | ||
| ### `time_shift` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but...
There is no info about relation between measure timeshifts and calendar cubes: how they are related, how matching happens, and how it is processed from the calendar's td definition: if interval+type are defined and when sql is defined.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know, it's been described in calendar cubes, but I think it would be useful to at least mention such options here with the link to the full description there...
| type: time | ||
|
|
||
| time_shift: | ||
| - type: prior |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no named examples: name + sql and name + interval + type
Bumps [form-data](https://github.com/form-data/form-data) from 4.0.1 to 4.0.4. - [Release notes](https://github.com/form-data/form-data/releases) - [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md) - [Commits](form-data/form-data@v4.0.1...v4.0.4) --- updated-dependencies: - dependency-name: form-data dependency-version: 4.0.4 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Cube generates a burst load of queries for refresh keys. We don't use a queue for cube store queries, but we use an in-memory cache inside QueryQueue. A cache miss leads to a problem where we start executing queries without debouncing. Cube executes refresh keys in parallel, which DDoSes Cube Store. It's a quick fix to fix this behavior.
…o CSV export bucket (#9810) * fix tsc build * fix(snowflake-driver): Set date/timestamp format for exporting data to CSV export bucket
The queue event bus was deprecated and is no longer needed.
…9817) Cube Store allows updating the heartbeat by path or queue id. Using queue id provides better performance and fixes possible concurrency issues, such as slippage
…ion (#9827) By default, it's specified as 60 seconds in presto-client. It uses a timer and cancels queries after it.
) Right now, we use both flags: used and touch. We already had LRU cache for a long time with the touch flag to reduce the number of updates in the Cache Store, but we didn't do it for the used. This leads to a situation where, for a schema with 100 pre-aggs, we will do 200 cache sets per 1 minute because the default refresh interval is set to 30 seconds.
List of changes: - Parse explicit `DISTINCT` option with set operators (e.g. `UNION DISTINCT`) - `array_agg` function can now be prefixed with `pg_catalog.` - New introspection tables are supported: - `pg_auth_members` - `pg_available_extension_versions` - `pg_cast` - `pg_event_trigger` - `pg_foreign_data_wrapper` - `pg_foreign_server` - `pg_foreign_table` - `pg_language` - `pg_locks` - `pg_operator` - `pg_rewrite` - `pg_tablespace` - `pg_timezone_abbrevs` - `pg_timezone_names` - `pg_user_mapping` - New introspection functions are supported: - `pg_is_in_recovery` - `pg_postmaster_start_time` - `pg_tablespace_location` - `txid_current` - System field `xmin` added to the following introspection tables: - `pg_am` - `pg_attribute` - `pg_class` - `pg_constraint` - `pg_description` - `pg_extension` - `pg_index` - `pg_namespace` - `pg_proc` - `pg_type` - `pg_namespace`'s `nspacl` field now has correct type (`List(Utf8)`) - `AGE` function now accepts values of type `xid` - `"char"` casts are being replaced with `text` casts - `xid` casts are being replaced with `unsigned int` casts - New `PgType`s added: - `[ARRAY]PGAM` - `[ARRAY]PGCAST` - `[ARRAY]PGEVENTTRIGGER` - `[ARRAY]PGEXTENSION` - `[ARRAY]PGFOREIGNDATAWRAPPER` - `[ARRAY]PGFOREIGNSERVER` - `[ARRAY]PGLANGUAGE` - `CTID` system field is replaced with `NULL` in data queries Signed-off-by: Alex Qyoun-ae <[email protected]>
Check List