#community-help

Issues with Typesense Search and JSON Formatting

TLDR Babin had issues with not getting all fields in a search. The problem was due to a JSON formatting extension in VS Code. Jason also clarified the requirement of query_by in multi-search POST method.

7mo

Join the chat

Mar 16, 2023 (7 months ago)

Photo of md5-aece7b06eda2a85a5bcfb5fd39332e2c

Babin

08:25 PM

Hi Jason
I am using below search


{
    "searches": [
        {
            "collection": "nic-items",
            "q": "-R - ",
            "page": 1,
            "per_page": 250,
            "include_fields": "id,sku,description,categoryName,brand,packSizeDescription"
        }
    ]
}

However I don't get all fields that are mentioned in include_fields
This is what we get

$Image 1 for Hi <@4L6c7> I am using below search ```<https://xxxxxxxxxxxxx.typesense.net/multi_search?query_by=sku,brand,description> { "searches": [ { "collection": "nic-items", "q": "-R - ", "page": 1, "per_page": 250, "include_fields": "id,sku,description,categoryName,brand,packSizeDescription" } ] }``` However I don't get all fields that are mentioned in include_fields This is what we get$

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

08:36 PM

~~Are all those fields present in all the documents?~~

Babin

08:38 PM

will that matter, one document could have brand, but not other one, we created some of the fields as optional in collection schema

Jason

08:38 PM

I meant to say, does that particular example document you shared have those fields?

If it does, could you DM me your cluster ID? I can take a closer look

Babin

08:50 PM

if [[ $# -eq 3 && $1 == 'get-single-document' ]]
then
    curl "${TYPE_SENSE_HOSTURL}/collections/${2}/documents/${3}" \
                                             -X GET \
                                             -H "X-TYPESENSE-API-KEY: ${TYPE_SENSE_API_MASTER_KEY}"
                                             
fi

This one gives me more than one documents

08:50

Babin

08:50 PM

Am I missing anything

09:03

Babin

09:03 PM

This is the exported JSONL

Jason

09:19 PM

Will take a look in about 15 mins

Babin

09:19 PM

Thanks

Jason

09:50 PM

In the JSON response you shared, I do see other fields for that SKU

Babin

09:50 PM

Let me check

09:50

Babin

09:50 PM

I might have been missing something very basic

09:57

Babin

09:57 PM

Thanks Jason, you know what happened. I was using a JSON formatter in VS Code, I found on whatever file I do format, it kept bringing a file from cache, Then I started investigating other collection, which is a small test collection. And I found the root cause of that stupid extension

09:58

Babin

09:58 PM

Thank you very much

10:00

Babin

10:00 PM

Once quick question I have, if you don't mind.
In multi-search POST method, is it mandatory to send query_by

The GET search without query_by works .

${TYPE_SENSE_HOSTURL}/collections/${2}/documents/search?q=*&amp;page=1&amp;per_page=250&amp;exclude_fields=images,salesSheet

Jason

10:12 PM

For q=* queries, query_by is not required. Otherwise it is required

Babin

10:12 PM

got it thanks

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Multiple Filters and JSON Requests in Typesense

Manish asked about multiple filter_by arguments, JSON input, and using multisearch. Jason offered typesense documentation links, examples, and how to use JSON formatted requests with multisearch. Ed shared a similar use case.

3mo

Querying and Indexing Multiple Elements Issues

Krish queried fields with multiple elements, which Kishore Nallan suggested checking `drop_tokens_threshold`. Krish wished to force OR mode for token, but Kishore Nallan admitted the feature was missing. Krish was able to resolve the issue with url encoding.

10mo

Moving from Algolia to Typesense: Questions and Answers

Juan sought advice from Kishore Nallan about moving from Algolia to Typesense, handling MultiSearch, setting parameters, checking imported documents, and a specific syntax query.

20mo

Cold Start Problem with Dynamic Collections

Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.

4mo

Resolving Typesense Analytics "top_queries" Collection Issue

Zain faced issues with typesense analytics and an empty "top_queries" collection. Jason and Kishore Nallan assisted in troubleshooting, identified a bug, and suggested a fix in `0.25.0.rc66`. The fix worked for Zain.

1mo