summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (from: 9a96acd)
raw | patch | inline | side by side (from: 9a96acd)
author | Sebastian Harl <sh@tokkee.org> | |
Tue, 6 Oct 2015 19:47:34 +0000 (21:47 +0200) | ||
committer | Sebastian Harl <sh@tokkee.org> | |
Tue, 6 Oct 2015 19:47:34 +0000 (21:47 +0200) |
Instead of letting the query implementation write JSON directly, let them emit
objects to a store-writer. This allows for more powerful and centralized
post-processing of the data and avoids code-duplication by moving all logic of
how to write out the data to the core. Also, this had a couple of nice side
effects and allowed for further simplication:
- The TIMESERIES command is now handled by the front-end (based on a FETCH of
the respective metric data); query plugin no longer have to implement this.
- All protocol specific information is now handled by the frontend; query
plugins no longer have to handle this (response-type).
- Further separation of the memory-store and generic store code.
objects to a store-writer. This allows for more powerful and centralized
post-processing of the data and avoids code-duplication by moving all logic of
how to write out the data to the core. Also, this had a couple of nice side
effects and allowed for further simplication:
- The TIMESERIES command is now handled by the front-end (based on a FETCH of
the respective metric data); query plugin no longer have to implement this.
- All protocol specific information is now handled by the frontend; query
plugins no longer have to handle this (response-type).
- Further separation of the memory-store and generic store code.
No differences found