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
{{ message }}
This repository was archived by the owner on Aug 23, 2023. It is now read-only.
Copy file name to clipboardexpand all lines: devdocs/expr.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -86,9 +86,10 @@ consolidateBy(
86
86
"max"
87
87
)
88
88
```
89
-
90
-
parsing starts at the root and continues until leaves are resolved.
91
-
Execution follows, and it happens the other way around (first leaves are fetched, then functions are applied until we hit the root)
89
+
There's 2 important information flows to be aware of: parsing and after it, execution.
90
+
* Parsing starts at the root and continues until leaves are resolved, and we know which series need to be fetched.
91
+
* Execution happens the other way around: first the data at the leaves is fetched, then functions are applied until we hit the root.
92
+
At that point function processing is complete; we can do some final work (like merging of series that are the same metric but a different raw interval, and maxDatapoints consolidation) and return the data back to the user.
92
93
93
94
So:
94
95
1) at parse time, consolidation settings encountered in consolidateBy calls are passed down the tree (e.g. via the context, typically until it hits the data request.
0 commit comments