Is it possible to use not-in query in Typesense? In algolia, it is possible with

index.search('query', {
  facetFilters: 'Name:-John'
})

The "-" operator is only supported for query strings at the moment, and not inside filters.

query_by ?

Correct

let documents = {
  'id': '124',
  'company_name': 'Stark Industries',
  'num_employees': 5215,
  'country': 'USA'
},
{
  'id': '125',
  'company_name': 'Apple',
  'num_employees': 20000,
  'country': 'USA'
},

Let’s say I have these documents. When I want to retrieve the first data by filtering

company_name !==Stark Industries

How can I achieve this?

?q=-stark -industries

will exclude both those tokens from search results.

query_by?

Query by on the field you wish to query, which in this example is

company_name

So, would query look like this?

let searchParameters = {
        'q':'company_name',
       'query_by':'?q=-stark -industries',
      }
   const result =  await client.collections('users').documents().search(searchParameters)

No, like this:

let searchParameters = {
        'q':'-stark -industries',
'query_by':'company_name'
      }
   const result =  await client.collections('users').documents().search(searchParameters)

Working, thanks! How many parameters does typesense allow for

q

? above example has 2 parameters.

q

is a search query which is really a lust of keywords / tokens you are searching for. When a keyword is prefixed with a

-

it just tell typesense to treat it as an exclusion explicitly. You can have as many tokens as you want, but as you add more tokens, things can become slower.

OK! Thank you so much!!!

👍

One more question, does q parameter support string[]?

Yes you can query array of strings.

const userIdList = [''] // This contains 850 user ids
let searchParameters = {
        'q':`${userIdList}`,
       'query_by':'userId',
      }
      try{
        const result =  await client.collections('users').documents().search(searchParameters)
        console.log(result['found']);
      }catch(e){
          console.log(e);
      }

When I run this code in Typesense cluster, These errors were emitted.

Request #1619079225148: Request to Node 0 failed due to "ECONNRESET socket hang up"
Request #1619079225148: Sleeping for 0.1s and then retrying request...
Request #1619079225148: Request to Node 0 failed due to "ECONNRESET socket hang up"
Request #1619079225148: Sleeping for 0.1s and then retrying request...
{ Error: socket hang up
    at createHangUpError (_http_client.js:332:15)
    at TLSSocket.socketOnEnd (_http_client.js:435:23)
    at TLSSocket.emit (events.js:203:15)
    at TLSSocket.EventEmitter.emit (domain.js:448:20)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  code: 'ECONNRESET',

Query should be string but is sent as a list in your example.

up to 840 lists, this worked as mentioned above. https://typesense-community.slack.com/archives/C01P749MET0/p1619075994204700?thread_ts=1619073087.199300&cid=C01P749MET0

What I meant is you can query a field whose type is a

string[]

. The

q

parameter must be a string. The

query_by

parameter must also be a comma separated string of field names.

Ok, So when I want to filter value from array of strings, how can I achieve this?

I presume you want to use the exclusion operator also?

Yes

Send a space separated list of IDs, like

user1 user2 -user3

(here user3 is getting excluded)

OK, I will try

Can you try setting

num_typos

to 0? The

q

field is not technically meant to be used this way with so many tokens. So what I have suggested might not work for large values. In any cases, I think you should run Typesense locally on your machine and check the logs to see if some error shows up when you query this way. Or, the query might just be taking a really long time and timing out because of the number of tokens used.

not working…

So is the query containing only exclusion tokens?

Yes, only exclusion tokens.

How many records are there in the collection being queried?

around 2500

Hard to say exactly what's going wrong. Not sure if the dataset can be shared. But if you can, email me (even another sample data set that exhibits the same problem is fine) and the exact query used and perhaps I can find out what's going wrong.

Or can I use DM on Slack?

Yeah sure