s-gal

@kishorenc That's great. Is it possible to put brackets in the statements if you have a more complex scenario like: (grade:>10 || is_premier: true) && gender:="female"

Should this feature also work in combination with scoped search keys? I have a problem and do not think the error is on my side... I defined a scoped key...

@kishorenc yes the filter in the scoped search key is something like: `(grade_math:=1 || grade_english:=2)` But now my problem is, if i set the filter_by attribute inside the multi_search endpoint...

@kishorenc thanks for your effort. as said my example is a lot bigger and seemes to work like for 80% of the records... it's just weird... i try to put...

@kishorenc thanks for the idea, but yes i am working for a company and its sensitive data and i am not allowed to share

@kishorenc the collection i have, has over 100 data fields in all kind of different types and the collection is over 50000 entries big... Not sure exacly if i leave...

@kishorenc i just reproduced the problem and sent you all needed data and informations to reproduce my problem to the email address you mentioned....

@kishorenc error occurs also with `/multi_search` end-point... wondering if the size of the API-KEY is the problem... if i add to the scoped key something like shipment_unit_code:=[`TEST1`,`TEST2`.....] it seemes like...

Also just tested it with the newest typesense version of `0.25.0.rc45` just in case you might have fixed it already accidentally in the last weeks but it's not the case....

@kishorenc yes now more complicated filters are working and this helps a bit. Seemes to me as you doubled the limit? We probably still could face problems in the future...