-
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
With MultiTenant deploy this.runScheduledRefresh(context, queryingOptions);
context is null
#1904
With MultiTenant deploy this.runScheduledRefresh(context, queryingOptions);
context is null
#1904
Comments
I am not able to reproduce this issue on my local machine: Config: module.exports = {
contextToAppId: (ctx) => {
console.log('contextToAppId', ctx);
return `CUBEJS_APP`
},
contextToOrchestratorId: (ctx) => {
console.log('contextToOrchestratorId', ctx);
return `CUBEJS_APP`
},
scheduledRefreshContexts: async () => {
return [{
authInfo: {
myappid: "demoappid",
u: {
bucket: "demo"
}
}
}]
},
}; Result:
I have no ideas. |
@ovr l mean without scheduledRefreshContexts config cube.js will throw exception . scheduledRefreshContexts must config when running with contextToAppId ? |
Run into the same issue when you use authInfo in preAggregationsSchema.
And it will complain |
Yes, because Cube.js is refreshing pre-aggregations/cache in the background, it's impossible to generate context(s) on the fly. You should declare I will introduce a check to write an error message about it. |
@ovr thanks, offical docs would description this for users who what use cube.js in multitenant environment |
Describe the bug
To Reproduce
run with express and config
Version:
[e.g. 0.25.30]
Additional context
maybe this cause
https://github.com/cube-js/cube.js/blob/master/packages/cubejs-server-core/src/core/server.ts#L228
cube.js config
The text was updated successfully, but these errors were encountered: