https://typesense.org logo
Join Slack
Powered by
I've been playing with the federated search this w...
# community-help
j
I've been playing with the federated search this week and it's fantastic, thanks again @Fanis Tharropoulos et al. for your work on this. Am I right in thinking that the 
pinned_hits
hasn't been implemented yet? I couldn't get it to work today so I just wanted to check whether that's the case, rather than a syntax error at my end.
f
Are you referring to the 
pinned_hits
parameter in the query parameters?
j
Yes that's right; I tried passing them both globally and inside the 
searches
array but they seem to get ignored in both instances
message has been deleted
f
I'll have to debug and get back to you
j
Thanks very much.
k
If you want to pass 
pinned_hits
globally, it has to be as part of the GET URL parameter, and not inside the POST payload.
j
hi @Kishore Nallan, thanks for getting back to me. I'm not sure I follow, what 
GET
URL are you referring to? I tried passing it to the 
POST <https://xxxxxxxx-1.a1.typesense.net/multi_search?pinned_hits=1597008:1>
request but it had no effect there either...
Actually, passing it as a URL param is removing the post from it's "usual" spot but it's not appearing in the position that I'm passing it. It looks like postman is escaping the URL param 
pinned_hits=1596779%3A1
, could this be the problem? Edit: Spoke to soon, I was able to switch off escaping but it doesn't seem to have helped.
k
Ok will check and get back to you.
🙌 1
Ok, we only support pagination parameters for now. Can you please create a Github issue for this? We will track it as a feature request and add to our roadmap.
Open in Slack
PreviousNext
Powered by