Bjørn Christian Seime
Bjørn Christian Seime
@nehajatav Could provide the output of the following command? The utility must be executed on a container node. ```sh vespa-get-config -n vespa.config.search.dispatch -i feed/component/dispatcher. | grep topKProbability ``` There are...
@nehajatav The command you listed does not include the content cluster name as suffix to config id. ``` $ vespa-get-config -n vespa.config.search.dispatch -i feed/component/dispatcher. |grep topKProbability ``` You can use...
Not directly, an internal third-party library `okta_sso_java_common` invoked a method that was removed in `jjwt-api`. That particular method was not deprecated, but was removed as part of some other related...
A suggestion is to upgrade jjwt everywhere else, and keep existing version for that particular module.
@ketankhairnar We intend to create a new or extend an existing example in https://github.com/vespa-engine/sample-apps. Feel free to submit a contribution there.
@ketankhairnar FYI https://blog.vespa.ai/announce-tokens-and-anonymous-endpoints/#data-plane-token-authentication
Agree with @yngveaasheim. The `Searcher` API is a too high-level abstraction to observe the complete latency. This is not possible with today's Searcher API, and even the low level async...
Resetting priority. This is part of larger effort to evaluate all existing container metrics.
Yes, this is clearly a bug.