mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-20 15:36:31 +01:00
463ea6897b
* vmselect/promql: enable search.maxPointsPerTimeSeriesSubquery for sub-queries * vmselect/promql: cleanup * vmselect/promql: rename config flag * vmselect/promql: add tests * vmselect/promql: use test object instead of log * vmselect/promql: fix posible panic is subquery has more points. add description * vmselect/promql: update tests descriptions * vmselect/promql: update doInternal validation * vmselect/promql: fix linter * vmselect/promql: fix linter * vmselect/promql: update documentation and release notes * wip - Properly apply -search.maxPointsSubqueryPerTimeseries limit to subqueries. Previously the -search.maxPointsPerTimeseries limit was unexpectedly applied to subqueries if it was smaller than the -search.maxPointsSubqueryPerTimeseries . - Clarify docs for -search.maxPointsSubqueryPerTimeseries command-line flag . - Document -search.maxPointsPerTimeseries and -search.maxPointsSubqueryPerTimeseries flags at https://docs.victoriametrics.com/#resource-usage-limits . - Update docs/CHANGELOG.md . Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2922 Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com> |
||
|---|---|---|
| .. | ||
| active_queries.go | ||
| aggr_incremental_test.go | ||
| aggr_incremental.go | ||
| aggr_test.go | ||
| aggr.go | ||
| binary_op.go | ||
| eval_test.go | ||
| eval.go | ||
| exec_test.go | ||
| exec.go | ||
| memory_limiter_test.go | ||
| memory_limiter.go | ||
| parser.go | ||
| rollup_result_cache_test.go | ||
| rollup_result_cache.go | ||
| rollup_test.go | ||
| rollup_timing_test.go | ||
| rollup.go | ||
| timeseries_test.go | ||
| timeseries.go | ||
| transform_test.go | ||
| transform.go | ||
| tzdata.go | ||