-
Couldn't load subscription status.
- Fork 0
chore: update fork to v0.36.11 #11
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
chore: update fork to v0.36.11 #11
Conversation
…'s SELECT (cube-js#8466) * chore(schema-compiler): Move backAliasMembers*() from PreAggreggations to BaseQuery * chore(schema-compiler): remove Ramda from BaseGroupFilter * chore(schema-compiler): improve getSqlGenerator() by removing duplicate calls to getDbType() * chore(schema-compiler): improvement in extractFilterMembers * chore(schema-compiler): Improvement in evaluateSymbolSql() * fix(schema-compiler): For views, propagate FILTER_PARAMS to inner cube SELECT * chore(schema-compiler): add tests for FILTER_PARAMS propagation * chore(schema-compiler): fix yaml-compiler tests * fix(schema-compiler): fix backalias resolution in FILTER_PARAMS to exclude segments
…exps to statics (cube-js#8675) * Replace lazy_static with LazyLock in many places * Replace lazy_static with Once for testing logger init * Remove unused testing logging static in config * Move more static regexps to LazyLocks
* Bump datafusion * Add tests for join with coercion execution
…ptions (cube-js#8618) * Add description to CubeMetaTable and CubeMetaColumn * Fill pg_description table with cube descriptions
Explain how dev environments are allocated one per user and how they are accessed. I mentioned this twice. If you think it's overkill, we can remove one :)
Add description from dbt manifest
… of results were incorrectly applying sorting from the original query and also were getting default ordering applied when the query ordering was stripped out (cube-js#8060) Thanks @rdwoodring! * fix(api-gateway) fix(schema-compiler): fixes an issue where queries to get the total count of results were incorrectly applying sorting from the original query and also were getting default ordering applied when the query ordering was stripped out * fix(api-gateway): add missing semicolon --------- Co-authored-by: Ryan Woodring <rwoodring@systemsalliance.com>
…yd-widen ! * updated jsonwebtoken in all packages * fix linting error, address other CVE * address tsc failure * reverted the jsdom change in playground * fixed yarn lock file * added the jsdom update back in
…tensionService DIServices (cube-js#8625)
* update * update
Added support for pre-aggregations for ksqldb using select statement and direct load from kafka
* feat(cubestore): implement date_bin() * add tests for date_bin udf in cubestore * remove obsolete stuff * remove debug logs + rename * remove debug logs
…cube-js#8693) * Extract user change tests to separate module * Add LoadRequestMeta to generated query from TestConnectionTransport * Turn panics into errors in TestConnectionTransport::load
…ping (cube-js#8678) * feat(cubejs-client/playground): new query builder * fix react ts errors * fix(cubejs-client/playground): typings * fix(cubejs-client/playground): e2e tests * fix(cubejs-client/playground): e2e tests * 2 * fix(cubejs-client/playground): e2e tests * 3 * fix(cubejs-client/playground): e2e tests * 4 * fix(cubejs-client/playground): e2e tests * 5 * fix(cubejs-client/playground): e2e tests * 6 * fix(cubejs-client/playground): e2e tests * 7 * fix(cubejs-client/playground): e2e tests * 8 * fix(cubejs-client/playground): e2e tests * 9 * fix(cubejs-client/playground): e2e tests * 10 * fix(cubejs-client/playground): e2e tests * 11 * fix(cubejs-client/playground): e2e tests * 12 * fix(cubejs-client/playground): e2e tests * 13 * fix(cubejs-client/playground): e2e tests * 14 * fix(cubejs-client/playground): e2e tests * 15 * fix(cubejs-client/playground): graphql raw response * fix(cubejs-client/playground): graphql raw response * 2 * feat(cubejs-playground): add chart prototyping * feat(cubejs-playground): add chart prototyping * 2 * feat(cubejs-playground): update query builder * fix(cubejs-playground): update build command * fix(cubejs-playground): update build command and vizard version * fix(cubejs-playground): update build command * fix(cubejs-playground): update build command --------- Co-authored-by: Alex Vasilev <vaspiring@gmail.com>
BREAKING CHANGE: Node.js is EOL, it was deprecated in v0.35.0
BREAKING CHANGE: Starting from v0.32, Cube Store is used as default cache and queue engine. Article: https://cube.dev/blog/replacing-redis-with-cube-store
BREAKING CHANGE: Removing this method since Cube is designed and supposed to be run as a cluster, rather than a serverless application, in a production setting. Use the Orchestration API instead
…dentity auth for export bucket (cube-js#8792)
…s (CMK) (cube-js#8791) * docs: Data-at-rest encryption in Cube Store and customer-provided keys (CMK) * . * Update docs/pages/product/workspace/encryption-keys.mdx Co-authored-by: Sam Hughes <sam@cube.dev> * Describe layers * . --------- Co-authored-by: Sam Hughes <sam@cube.dev>
* feat(cube): Renaming of Post Aggregate into Multi Stage * update
parallelism: The number of threads RocksDB will use for all background operations. Even if you increase the max_background_jobs but keep parallelism as 1, it won’t lead to a lot of performance increase. Ideally, this option should be kept equal to the number of cores in your machine. max_background_jobs is 2, but parallelism was 1. Must be aligned.
This commit introduces a new style Role Based Access Control framework
for cubes. User can now define `accessPolicies` on Cubes and Views which
will be evaluated into `queryRewrite` and visibility rules.
This commit introduces a new config: `contextToRoles(context):
string[]`. It should return a list of user role names based on the
request context. Access Policies are defined per Cube x Role name like
```
access_policy:
- role: "manager"
conditions:
- if "{ security_context.isNotSuspended }"
row_level:
filters:
- member: `access_level`
operator: lt
values: [2]
member_level:
includes: "*"
excludes: [`top_secret_field`]
```
Each policy can define a `row_level` and `member_level` rules.
Row level rules can be defined as a list of filters or `allow_all: true`
Member level rules should specify a list of "included" members that the
user with a given role is allowed to see.
When evaluating Cube and View level policies:
- row level filters are joined via AND (least permissive policy wins)
- member level policy at the view always wins (you can expose a hidden
member of a Cube on a View)
Policies can reference `security_context` (lowercase) when evaluating
policy conditions and filter values.
* feat: init * fix: path * fix: set default token path
v0.36.11
c5011fb to
124bb38
Compare
| }).filter(R.identity).map(this.newTimeDimension.bind(this)); | ||
| this.allFilters = this.timeDimensions.concat(this.segments).concat(this.filters); | ||
|
|
||
| this.collectAllMemberNames(); // Ensure member names are computed so that they are not lazily added during join computation |
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.
This change is a bit unexpected. Is this something you really wanted to add to the fork and deviate from upstream?
I thought we just wanted to bump the versions
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.
Yes, this is a cherry-pick of this fix: cube-js#9942
Without this line we're having a bug where Cube would add more joins than necessary, killing performance. That's what was preventing us from using more recent versions than 0.35 until now.
git merge v0.36.11).github/workflows/image-build.yamlandrust/cubestore/gorgias.Dockerfileaccordingly