-
Notifications
You must be signed in to change notification settings - Fork 53
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
Is it possible to disable aggregation key in schema during request? #158
Comments
Hi Alex, it is not possible now but definitely could be useful. |
Great decision! The main thing that it affected the performance |
For me, when i remove aggregation list from schema the time response is about 45 ms and with aggregation list this value is about 1,5 seconds And it would be cool to provide the list which aggregations should be loaded in GET query |
Yeah, definitely. 1.5 seconds is too long if 45 ms is possible. I have it on my ToDo list. I will implement that probably by Friday. Is it "asap" for you ? |
👍 Great! |
@cigolpl it would be cool! |
@cigolpl cool! i check it today! |
hi @cigolpl If i make search with no aggregations like this
I receive this error when i make request with aggregation like From logs:
The
I also tried to remove
|
Hi Alex, thanks for feedback! Could you temporary change your aggregations for: "aggregations": {
"category_tree": {
"type": "terms",
"field": "category_identificator",
"size": 40,
"title": "Categories"
},
"brand": {
"type": "terms",
"field": "brand",
"size": 40,
"title": "Brands"
}
} and see if |
Great! This works nice for now! 👍 |
Great but there can be a small problem. If you define I've made a mistake some time ago introducing How is your app working with that new temporary configuration ? |
All works perfectly, i didn't get any problems after defining aggregations as an object |
Oo, that's really cool |
The problem is about how to temporary disable aggregation processing during requests? The aggregation takes a lot of time and in some requests i want to disable it
The text was updated successfully, but these errors were encountered: