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
Because of this (code path) difference, adding query-related features requires implementing the logic in both places (which has led to bugs).
I propose rewriting this block of code (i.e. the query-related logic contained in QueryRpc) to process queries/annotations/etc and return data, moving it away from handleQuery. The responsibility of QueryRpc.handleQuery would then simply be to attach a formatter to the data, while the responsibility of GraphHandler.doGraph would be to turn the data into a graph (via gnuplot).
The text was updated successfully, but these errors were encountered:
Right now, GraphHandler.doGraph (
opentsdb/src/tsd/GraphHandler.java
Line 126 in 08acb73
opentsdb/src/tsd/GraphHandler.java
Line 193 in 08acb73
QueryRpc.handleQuery has similar logic, but actually does things asynchronously (
opentsdb/src/tsd/QueryRpc.java
Line 112 in 08acb73
Because of this (code path) difference, adding query-related features requires implementing the logic in both places (which has led to bugs).
I propose rewriting this block of code (i.e. the query-related logic contained in QueryRpc) to process queries/annotations/etc and return data, moving it away from handleQuery. The responsibility of QueryRpc.handleQuery would then simply be to attach a formatter to the data, while the responsibility of GraphHandler.doGraph would be to turn the data into a graph (via gnuplot).
The text was updated successfully, but these errors were encountered: