fix(query)!: Remove epsilon parameter from VectorQuery

[booleanhunter]

EPSILON is a VECTOR_RANGE-only attribute. So when emitted inside the KNN bracket, Redis responds with:

ResponseError: Error parsing vector similarity parameters:
range query attributes were sent for a non-range query

• Remove epsilon kwarg, set_epsilon() method, and epsilon property
• Remove EPSILON emission from _build_query_string and params
• Add unit test to assert contruction-time rejection
• Add an integration-suite regression test for the rejection

Does not impact VectorRangeQuery

Any potential risk?

• The population of working callers being broken by this fix is empty. It will be a breaking-change only if there are callers whose code worked before this change. There aren't
• The set of "callers who previously passed epsilon to VectorQuery" is the set of callers whose code was already crashing at execute time.

So, this fix does not introduce a new failure mode for any code that was previously succeeding.

---

Note

Medium Risk
Medium risk because it’s a breaking API change for callers passing epsilon/using set_epsilon/epsilon, though it prevents Redis execution-time errors by no longer generating invalid KNN query syntax.

Overview
Removes epsilon support from VectorQuery. The constructor kwarg, set_epsilon() method, and epsilon property are deleted, and EPSILON is no longer appended to the KNN query string or included in params.

Updates tests accordingly. Unit coverage that validated VectorQuery epsilon behavior is removed, and the combined-runtime-params test is adjusted to exclude EPSILON while keeping other runtime params (EF_RUNTIME, SEARCH_WINDOW_SIZE, USE_SEARCH_HISTORY, SEARCH_BUFFER_CAPACITY).

^{Reviewed by Cursor Bugbot for commit df0a5a2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jit-ci]

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

[booleanhunter]

Fixes Issue #611

[vishal-bala]

LGTM! Just a couple comments about how I think adding a regression test for this is a little bit overkill, since it's incredibly unlikely that someone would attempt to re-add that parameter.

Fine to have the integration test too, but also want to avoid a bloated test suite.

[booleanhunter]

Thank

LGTM! Just a couple comments about how I think adding a regression test for this is a little bit overkill, since it's incredibly unlikely that someone would attempt to re-add that parameter.

Fine to have the integration test too, but also want to avoid a bloated test suite.

That makes sense! I shall remove the regression test

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 947a2bd. Configure here.}