When logging features, the 'active_features' field isn't respected in the SLTR query and features that are not specified in active_features are returned in the _ltrlog without score values.
Sometimes you might want to execute your query on a subset of the features rather than use all the ones specified in the model. In this case the features not specified in active_features list will not be scored upon. They will be marked as missing. You only need to specify the params applicable to the active_features. If you request a feature name that is not a part of the feature set assigned to that model the query will throw an error.
This is a bit confusing to use as I've noticed that scores are also not returned if there's no match for features specified as active_features (see examples below). Would it make more sense to exclude features not specified in active_features from the "_ltrlog" altogether, or is there a reason they are included?
Expected behaviour
When sending an SLTR query with a subset of active_features specified, e.g.
I expected to only see the specified feature title_query returned in the _ltrlog. Instead, the returned response contains all features in the featureset, without score values for non-active features e.g.
When logging features, the 'active_features' field isn't respected in the SLTR query and features that are not specified in
active_features
are returned in the_ltrlog
without score values.The docs say:
This is a bit confusing to use as I've noticed that scores are also not returned if there's no match for features specified as
active_features
(see examples below). Would it make more sense to exclude features not specified in active_features from the"_ltrlog"
altogether, or is there a reason they are included?Expected behaviour
When sending an SLTR query with a subset of
active_features
specified, e.g.I expected to only see the specified feature
title_query
returned in the_ltrlog
. Instead, the returned response contains all features in the featureset, withoutscore
values for non-active features e.g.Expected:
Actual:
Steps to reproduce
The code to reproduce the issue can be found in a POC repo I've created here.
Index:
Create LTR index and featureset:
Case 1 - STLR query with all
active_features
Returns:
Case 2 - STLR query with single active feature
Returns:
Case 3 - Index doc without a description
SLTR query with
description_query
inactive_features
:Returns: