I'm querying galaxy -note20 but it's still includi...
# community-help
e
I'm querying galaxy -note20 but it's still including results with "Note20" in the title. Other negations with the dash/minus seem to work fine. What am I missing?
j
Could you share the collection schema and all the search parameters you're using?
e
sure
there just seems to be some weird things going on here
message has been deleted
message has been deleted
message has been deleted
I'm using InstantSearch Vue, with a few widgets. Maybe that's why theres three searches?
If there's anything I kind of miss from Typesense right now is some kind of "pro mode search" where you could search using regex, or at least some format to include/exclude different phrases and stuff like that, to really dial in a query, to find the right products (in my case).
@Jason Bosco do you have a clue what could be wrong?
it might be related to multiple negations? when I keep adding negations it seems the earlier negations are ignored, as if it's only taking a few negations?
k
@em1nos Are you able reproduce this on a small sample dataset (maybe just a few records) and by directly hitting the API? Is so, please share that and the query and I will be happy to dig into what is going wrong.
e
I have not tested that.
@Jason Bosco do you have an idea of what could be wrong, or should I try to reproduce this with a smaller dataset?
j
If you can reproduce it on a smaller dataset, that will help get to the bottom of the issue fastest
e
ok, I'll do that. I see Cloud has some hours for free, so I'll use some of those for testing, that's easiest for me since I don't really use the direct API on my own installation (I use InstantSearch and Laravel Scout Driver)
message has been deleted
So I could reproduce it with 4 records on the C loud service. Latest Typesense.
j
Could you share the cluster ID?
e
=== Typesense Cloud: p6yvc5sw8g1jeq74p ===
j
Cool, will take a closer look and keep you posted.
e
Thanks
k
Couldn't get to this today, plan to dive in tomorrow!
e
No worries! No hurry for me. But it might actually be a bug then since I could reproduce it so easily on Cloud (see screenshot above).
k
@em1nos I'm able to reproduce this issue on 0.22.2 but is fixed on the latest 0.23 RC builds.
I've also now added this as a test so will help prevent regressions in future.
e
that's awesome, thank you
🙌 1