Skip to content

Improve error messages for scripting vector calculations #91526

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
Open
Tracked by #84324
jdconrad opened this issue Nov 10, 2022 · 2 comments
Open
Tracked by #84324

Improve error messages for scripting vector calculations #91526

jdconrad opened this issue Nov 10, 2022 · 2 comments
Labels
>enhancement :Search Relevance/Vectors Vector search Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch

Comments

@jdconrad
Copy link
Contributor

The class bindings dotProduct, l1Norm, l2norm, and cosineSimilarity give confusing error messages when a user writes a script and either gives a non-existent field or a field that is not a vector type. We can detect this as part of the constructor for each of the class bindings and give improved error messages.
@jdconrad jdconrad self-assigned this Nov 10, 2022
@elasticsearchmachine elasticsearchmachine added the Team:Search Meta label for search team label Nov 10, 2022
@jdconrad jdconrad mentioned this issue Nov 10, 2022
Open
43 tasks
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

@javanna javanna added Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch and removed Team:Search Meta label for search team labels Jul 12, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@jdconrad jdconrad removed their assignment Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement :Search Relevance/Vectors Vector search Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@javanna @jdconrad @elasticsearchmachine