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.

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

[Feature Request] Federated Search Then Aggregate Data #381

Open
ice-ares opened this issue Sep 9, 2021 · 6 comments
Open

[Feature Request] Federated Search Then Aggregate Data #381

ice-ares opened this issue Sep 9, 2021 · 6 comments

Comments

@ice-ares
Copy link

ice-ares commented Sep 9, 2021

Description

Our app has a feature where we want to search for (query_by) some fields across multiple collections then aggregate the results of all those collections into a "Best Matches Globally" result with best hits and highlights.

Is it possible to add a feature that adds the same logic and behaviour of
GET ${TYPESENSE_HOST}/collections/:collection/documents/search to POST ${TYPESENSE_HOST}/multi_search ?

@kishorenc
Copy link
Member

@victor-oancea-leftclick-io 👋

Thanks for suggesting this feature.

For now, you can merge the results on client side: the text_match score returned in the hits can be used to rank results across collections.

@JZubero
Copy link

JZubero commented Aug 31, 2022

Same situation here. While I agree with @kishorenc that result merging could be done on the client side by utilizing the text_match score, sorting and pagination can get painful, especially with large result sets.

@ice-ares May I ask how you have solved this for now?

@marcopesani
Copy link

+1

@philefstat
Copy link

this feature would be super useful - handing pagination etc. client side is v painful

@jasonbosco
Copy link
Member

jasonbosco commented May 23, 2024

@jasonbosco
Copy link
Member

This feature is now available in 28.0.rc30 or above.

The description in this PR has usage instructions: #2051 (comment).

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

No branches or pull requests

6 participants