Bjørn Christian Seime

@PeriLara Try to specify floating point values as limits in the `predefined` expression as a workaround: `predefined(quality_spamness, bucket[0.0,1.0>, bucket[1.0,2.0>, bucket[2.0,inf>)`

We have now identified the underlying problem. A predefined bucket operator is given the type of the lower/upper bound values (double/long/raw/string). Each value evaluated from the `predefined` expression is converted...

@PeriLara Make sure to specify decimal for all bounds (`bucket[0,0.5>` => `bucket[0.0,0.5>`).

The grouping query documentation on `predefined` will be improved with https://github.com/vespa-engine/documentation/pull/2420.

https://github.com/vespa-engine/vespa/pull/27120 changes `StatisticsSearcher` to use the correct request timestamp. Previous timestamp did not account for initial request processing in Jetty. The `handled.latency` includes the latency up to the *start of...

Resetting priority. This is part of larger effort to evaluate all existing container metrics.

PR build broke: ``` 13:06:19 [ERROR] com.yahoo.search.significance.test.SignificanceSearcherTest.testSignificanceValueOnRecursiveQuery -- Time elapsed: 0.008 s