https://typesense.org logo
Join Slack
Powered by
if I run the search using those generated params a...
# community-help
k
if I run the search using those generated params as a 
filter_by
and not as an 
nl_query
it returns what I expect
j
Are you using a scoped search API key with an embedded filter, or any additional explicit filter_by in the search query, that might be filtering out the data?
These other sources of filter_by are ANDed to the generated params
k
This is a self hosted barebones deployment. I only have the default API key. No other 
filter_by
.
Querying through JS:
Copy code
const searchResults = await typesense
    .collections("agents")
    .documents()
    .search({
      q: "cx support familiar with Zendesk or tech support familiar with Jira",
      nl_query_debug: true,
      nl_query: true,
      nl_model_id: "openai-model",
      facet_by: ["country"],
      query_by:
        "experience.techExperience.roles,experience.techExperience.tools,experience.cxExperience.roles,experience.cxExperience.tools",
    });
j
Could you replicate the issue using a simple curl snippet like this, that creates the model (minus the API key), creates a collection with a few sample docs and then runs the NL query: https://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b
k
ok was just about to head out from the office but let me try to put this together a little later
My first test was running off a GCP Cloud Run instance so maybe that was an issue but I get the same result locally
j
CC: @Alan Martini could you look into this?
🙏 1
Open in Slack
PreviousNext
Powered by