-
Notifications
You must be signed in to change notification settings - Fork 233
fix: fix search in memory with AnyEmbedding #1696
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
Conversation
e484ff0
to
f96171f
Compare
Signed-off-by: Joan Fontanals Martinez <[email protected]>
f96171f
to
bc0e40d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why was AnyEmbedding
failing?
It does not have a computational backend attached, so it cannot stack or do anything on tensors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to change
_extract_embedding
directly to look at the type to the AnyTensor
and what about the compBackend, is it okey If I return the NumpyBackend for AnyTensor as default? |
Signed-off-by: Joan Fontanals Martinez <[email protected]>
d36a0b5
to
e7315e8
Compare
a41e3f7
to
4e013b4
Compare
Signed-off-by: Joan Fontanals Martinez <[email protected]>
4e013b4
to
2babe51
Compare
4d8a20a
to
57bf37b
Compare
Signed-off-by: Joan Fontanals Martinez <[email protected]>
57bf37b
to
bab8099
Compare
📝 Docs are deployed on https://ft-anytensor-in-memory-search-fix--jina-docs.netlify.app 🎉 |
Allows to do easy search in Memory when AnyEmbedding is used as with
TextDoc
orImageDoc
: