VictoriaMetrics/app/vlselect
Aliaksandr Valialkin 657988ac3a
app/vlselect: consistently reuse the original query timestamp when executing /select/logsql/query with positive limit=N query arg
Previously the query could return incorrect results, since the query timestamp was updated with every Query.Clone() call
during iterative search for the time range with up to limit=N rows.

While at it, optimize queries, which find low number of matching logs, while spend a lot of CPU time for searching
across big number of logs. The optimization reduces the upper bound of the time range to search if the current time range
contains zero matching rows.

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6785
2024-09-08 14:32:23 +02:00
..
logsql app/vlselect: consistently reuse the original query timestamp when executing /select/logsql/query with positive limit=N query arg 2024-09-08 14:32:23 +02:00
vmui app/{vmselect,vlselect}: run make vmui-update vmui-logs-update 2024-08-28 13:30:38 +02:00
main.go app/vlselect: add /select/logsql/stats_query_range endpoint for building time series panels in VictoriaLogs plugin for Grafana 2024-09-07 00:41:47 +02:00