-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Rollup joins across different data sources with different param allocators causing invalidations #8268
Comments
pauldheinrichs
changed the title
Orchestration API on multi datasource using improper driver
Multi datasource using improper driver for Orchestration / Pre-Aggregation cache checks
May 16, 2024
pauldheinrichs
changed the title
Multi datasource using improper driver for Orchestration / Pre-Aggregation cache checks
Druid Driver assuming wrong parameter argument for partitioned pre-aggregation
May 17, 2024
pauldheinrichs
changed the title
Druid Driver assuming wrong parameter argument for partitioned pre-aggregation
Druid Driver assuming wrong parameter argument for incremental partitioned pre-aggregation
May 17, 2024
pauldheinrichs
changed the title
Druid Driver assuming wrong parameter argument for incremental partitioned pre-aggregation
Rollup joins across different data source with different param allocators causing invalidations
May 19, 2024
pauldheinrichs
changed the title
Rollup joins across different data source with different param allocators causing invalidations
Rollup joins across different data sources with different param allocators causing invalidations
May 19, 2024
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When attempting to run the orchestration on a druid datasource to rebuild pre-aggregations. The following error is spit out in the API logs after running.
--- EDIT ---
Seems like this for me may be an underlying issue with something i'm working through. My API node is frequently assuming my druid models are my
default
driver param object in more than just orchestration. It infact is invalidating my pre-aggregations because it's assuming thedefault
driver. I do not have acube.js
file in my instance.Slack thread:https://cube-js.slack.com/archives/C04NYBJP7RQ/p1715737464066809
(IF i'm just doing it wrong... let me know 😓 )
Focusing on specifically
Error: org.apache.calcite.runtime.CalciteContextException: From line 4, column 81 to line 4, column 82: Column '$1' not found in any table
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It seems that this process isn't utilizing the druid based
?
expected variable but rather the postgres driver param in my case (which is redshift / postgres$1
syntax )IT would appear that this method is being called with a passed in
$1
argsVersion:
Latest version
The text was updated successfully, but these errors were encountered: