Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upStreaming query engine #3691
Comments
This comment has been minimized.
This comment has been minimized.
|
What sort of API are you imagining? Having to return the same time series names again and again could be expensive. |
brian-brazil
added
priority/Pmaybe
not-as-easy-as-it-looks
component/api
component/promql
and removed
component/api
labels
Jun 13, 2018
This comment has been minimized.
This comment has been minimized.
|
after the dev discussions at Promcon there are no objections that there would be no benefits from streaming in remote read and too complicated to be worth it in the promql. |
krasi-georgiev
closed this
Aug 14, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
brancz commentedJan 16, 2018
In order for us to be able to implement streaming APIs (#3690) the query engine also needs to be streaming. Currently it processes the entire query, and then returns the result.
@fabxc @gouthamve @brian-brazil