Skip to content
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

Expose usedPreaggregation through REST load API in prod mode #9078

Open
flochaz opened this issue Jan 8, 2025 · 2 comments
Open

Expose usedPreaggregation through REST load API in prod mode #9078

flochaz opened this issue Jan 8, 2025 · 2 comments
Assignees
Labels
enhancement New feature proposal

Comments

@flochaz
Copy link

flochaz commented Jan 8, 2025

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.

@igorlukanin
Copy link
Member

@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?

@igorlukanin igorlukanin self-assigned this Jan 8, 2025
@flochaz
Copy link
Author

flochaz commented Jan 8, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature proposal
Projects
None yet
Development

No branches or pull requests

2 participants