Skip to content
This repository was archived by the owner on Aug 23, 2023. It is now read-only.

Commit 53f9229

Browse files
committed
better words
1 parent 08c858c commit 53f9229

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

devdocs/expr.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -86,9 +86,10 @@ consolidateBy(
8686
"max"
8787
)
8888
```
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.
9293

9394
So:
9495
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

Comments
 (0)