This PR adds support for the potentiallyStale value in the feature search API. The value is added as a third option for state (in addition to stale and active). Potentially stale is a subset of active flags, so stale flags are never considered potentially stale, even if they have the flag set in the db.
Because potentially stale is a separate column in the db, this complicates the query a bit. As such, I've created a specialized handling function in the feature search store: if the query doesn't include potentiallyStale, handle it as we did before (the mapping has just been moved). If the query does contain potentially stale, though, the handling is quite a bit more involved because we need to check multiple different columns against each other.
This PR adds support for the
potentiallyStale
value in the feature search API. The value is added as a third option forstate
(in addition tostale
andactive
). Potentially stale is a subset of active flags, so stale flags are never considered potentially stale, even if they have the flag set in the db.Because potentially stale is a separate column in the db, this complicates the query a bit. As such, I've created a specialized handling function in the feature search store: if the query doesn't include
potentiallyStale
, handle it as we did before (the mapping has just been moved). If the query does contain potentially stale, though, the handling is quite a bit more involved because we need to check multiple different columns against each other.