Skip to content

recommend: hardcoded tensor field order #1251

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.

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

Open
wants to merge 4 commits into
base: mainline
Choose a base branch
from

Conversation

vicilliar
Copy link
Contributor

Change Summary

Test fix.
Personalization changes recommend such that the order of tensor fields is now deterministic based on the tensor_fields parameter instead of it being determined by the vespa return object. This updates the tests to hardcode the tensor field order.

Checklist

  • Tests have been added for changes
  • Documentation has been updated
  • Breaking changes are clearly identified
  • Python client changes linked or N/A

For new field types:

  • Tests cover score modifier usage of this new type
  • Test indexes updated to cover the new type for all APIs (add docs, search, partial update, etc.)

@vicilliar
Copy link
Contributor Author

Passing backwards compatibility test (Except for the global score modifiers known issue): https://github.com/marqo-ai/marqo/actions/runs/15869853517/job/44748192917

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants