-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[visualizations] Add aggs argument to custom requestHandlers #67916
Copy link
Copy link
Closed
Labels
Feature:ExpressionLanguageInterpreter expression language (aka canvas pipeline)Interpreter expression language (aka canvas pipeline)Feature:VisualizationsGeneric visualization features (in case no more specific feature label is available)Generic visualization features (in case no more specific feature label is available)bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of EffortSmall Level of Effortregression
Description
Metadata
Metadata
Assignees
Labels
Feature:ExpressionLanguageInterpreter expression language (aka canvas pipeline)Interpreter expression language (aka canvas pipeline)Feature:VisualizationsGeneric visualization features (in case no more specific feature label is available)Generic visualization features (in case no more specific feature label is available)bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of EffortSmall Level of Effortregression
Type
Fields
Give feedbackNo fields configured for issues without a type.
Somewhere in between migration to the new platform and the expressions-based vis infrastructure, it seems we are no longer providing an
aggsargument to customrequestHandlers.esaggs(the default request handler) usesaggs, however it appears it was left out of thevisualization_functionfallback which is used for custom handlers. We should add this argument back so that it doesn't break vis development for folks relying on aggs in custom request handlers.Related forum thread: https://discuss.elastic.co/t/how-to-access-aggregations-from-within-custom-request-handler/226445