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
Let's try to produce a report that gives number of hours by team by priority. Doing nested aggregation on teams.name and then reverse nested to group on priority and then nested to sum teams.hours double-counts hours because second nesting on teams knows nothing about upstream nesting as it is executed in context of request and as result it will lump hours for each team on request under the top level team aggregation. sum of hour under team is 10 and 20 but when we group again with priority( under each team ) and perform sum of hour its 30 means its considering two nested team objects. how to solve this issue?
Describe the bug
mapping:
Let's try to produce a report that gives number of hours by team by priority. Doing nested aggregation on teams.name and then reverse nested to group on priority and then nested to sum teams.hours double-counts hours because second nesting on teams knows nothing about upstream nesting as it is executed in context of request and as result it will lump hours for each team on request under the top level team aggregation. sum of hour under team is 10 and 20 but when we group again with priority( under each team ) and perform sum of hour its 30 means its considering two nested team objects. how to solve this issue?
Related component
Search:Aggregations
To Reproduce
mapping:
Expected behavior
expected result:
Additional Details
The text was updated successfully, but these errors were encountered: