Pinging @elastic/es-search-relevance (Team:Search Relevance)

I wonder if this shouldn't be a cluster feature / capability. Or, IIRC, IVF is behind a feature flag hence we might just add a check for that in the failing tests?

just noticed that @carlosdelest has just done something like that in #129766

I wonder if this shouldn't be a cluster feature / capability. Or, IIRC, IVF is behind a feature flag hence we might just add a check for that in the failing tests?

I haven't updated how we define the BBQ_IVF format, we still make use of the feature flag defined in DenseVectorFieldMapper#IVF_FORMAT.

The main issue here is with the -Dtests.jvm.argline="-Dbuild.snapshot=false" param as mentioned in the description. While for standard tests the feature flag for IVF is enabled, when using a release build, this is not the case, so even though we could potentially pick it randomly (given the seed), when resorting to VectorIndexType#fromString we would throw.

The proposed fix in this case is to account for the feature flag when choosing the valid values in the RescoreKnnVectorQueryIT, similarly to how we do in VectorIndexType#fromString.