Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

accept K parameter as float if there is no loss in the precision after rounding to the integer #1761

Merged
merged 2 commits into from
Sep 30, 2024
Merged

accept K parameter as float if there is no loss in the precision after rounding to the integer #1761

merged 2 commits into from
Sep 30, 2024

Commits on Sep 29, 2024

  1. accept K parameter as float if there is no loss in the precision afte… 

    …r rounding to the integer

- it cah be hard in some cliens (JS for example) to distinguish between INTEGERs and FLOATs - so we always bind FLOATs instead
- this create unnecessary error: "vector index(search): third parameter (k) must be a non-negative integer"
    @sivukhin
    sivukhin committed Sep 29, 2024
    Configuration menu
    Copy the full SHA
    4091efb View commit details
    Browse the repository at this point in the history

  2. build bundles

    @sivukhin
    sivukhin committed Sep 29, 2024
    Configuration menu
    Copy the full SHA
    80a10f9 View commit details
    Browse the repository at this point in the history