You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR fixes the 2nd Major issue in
#234, related
to Configuration and Querying Issues
Issue breakdown:
-
**Inconsistent k Parameter:** For hybrid searches, the dense search
LIMIT was tied to the final k parameter, while the sparse search used
its own secondary_top_k.
**Late Initialization of HybridSearchConfig:** The HybridSearchConfig
was initialized after the k parameter was calculated, which could lead
to incorrect behavior if the config was passed dynamically via `kwargs`.
Overview of the changes:
-
1. The __query_collection method now uses a separate `dense_limit` for
the dense search query.
If HybridSearchConfig is active, dense_limit is set to primary_top_k.
For dense-only searches, dense_limit defaults to the final k value,
preserving the existing behavior.
2. The hybrid_search_config is now initialized at the beginning of
`__query_collection`, ensuring that any `kwargs` overrides are handled
before `k` or `dense_limit` are calculated.
0 commit comments