You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We are heavily relying on pre-aggregation and relying on job API to force rebuilt of pre aggregation.
The API support cubes or preAggregation parameter but there is no way to know what cube or preAggregation is used by a given query.
Describe the solution you'd like
get usedPreaggregation detailed in prod mode
Describe alternatives you've considered
The naive alternative was to try to deduct the cube targeted using the dimension of the query but it is to reliable and force us to refresh the entire set of pre aggregation with in a cube.
The text was updated successfully, but these errors were encountered:
@flochaz Thanks for filing this! Just one more time, could you please explain, in the simplest terms possible, what are you trying to achieve here? Run a query, understand if it targeted a pre-aggregation, then refresh that pre-aggregation via the Orchestration API? Is this a correct guess? If so, why would you like to do it this way?
Queries to create the pre aggregations are quite complex in our case and take db loads quite heavily so we limit the auto refresh to every few hours but sometime client want the latest data so we offer as an extra option to force the refresh for a specific graph/query. I hope it clarify things. But maybe there is other way to achieve this though
Is your feature request related to a problem? Please describe.
We are heavily relying on pre-aggregation and relying on job API to force rebuilt of pre aggregation.
The API support cubes or preAggregation parameter but there is no way to know what cube or preAggregation is used by a given query.
Describe the solution you'd like
get
usedPreaggregation
detailed in prod modeDescribe alternatives you've considered
The naive alternative was to try to deduct the cube targeted using the dimension of the query but it is to reliable and force us to refresh the entire set of pre aggregation with in a cube.
The text was updated successfully, but these errors were encountered: