Issues with Indexing Data using Typesense in Go
TLDR Konrad was having trouble with a "Forbidden" error using Typesense in Go when indexing data remotely. David offered multiple troubleshooting steps and suggestions. Ultimately, Konrad discovered the issue lied within the application code.
Sep 03, 2023 (3 weeks ago)
Konrad
08:09 PMAny ideas how to solve this or figure out what's wrong?
Konrad
08:12 PMKonrad
08:18 PMKonrad
08:19 PM
David
08:32 PMDavid
08:36 PM{"message": "Forbidden - a valid x-typesense-api-key header must be sent."}Konrad
08:37 PMKonrad
08:38 PM _, err = typesenseClient.Collection("tasks").
Documents().
Import(typesenseTasks, &api.ImportDocumentsParams{
Action: pointer.String("upsert"),
BatchSize: (100),
}) Konrad
08:38 PMDavid
08:39 PMKonrad
08:40 PMKonrad
08:40 PMKonrad
08:40 PMKonrad
08:41 PMDavid
08:42 PMDavid
08:43 PMDavid
08:43 PMpointer.String("upsert")David
08:44 PMDavid
08:46 PMDavid
08:46 PMAction: "upsert" insteadKonrad
08:48 PM*string (not string) in the params structKonrad
08:49 PMDavid
08:52 PMDavid
08:53 PMDavid
08:55 PMDavid
08:56 PMcurl -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -X POST --data-binary @documents.jsonl \
'' Konrad
08:57 PMDavid
08:57 PMDavid
08:57 PMjq -c '.[]' documents.json > documents.jsonlKonrad
09:01 PMDavid
09:01 PMDavid
09:01 PMDavid
09:01 PMparams := &api.ImportDocumentsParams{Action: pointer.String("create")}
responses, err := typesenseClient.Collection(collectionName).Documents().Import(documents, params)Konrad
09:01 PMDavid
09:02 PM_, err =should that be
_, err :=?Konrad
09:02 PMerr is already defined in my caseKonrad
09:03 PM:= defines a new variable on the fly but it will give you a compile error when you try to redeclare an existing variableDavid
09:07 PMDavid
09:09 PMDavid
09:09 PMDavid
09:09 PMKonrad
09:10 PMDavid
09:11 PMKonrad
09:11 PMSep 04, 2023 (3 weeks ago)
Konrad
08:36 AMKonrad
08:36 AMKonrad
09:13 AM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Data Load Issues on Ecommerce Platform
Dương requested help with Typesense data load issues on non-localhost systems. Kishore Nallan and David helped him isolate the problem. It was finally resolved when Dương identified and corrected a router configuration issue.
1Issues Running Typesense on AWS Fargate
Sulove is struggling with administrative operations on Typesense on AWS Fargate, and getting errors. Kishore Nallan suggested checking if data wasn't persisting on Fargate, despite no resolution being achieved.
Trouble with Document Error in Indexing
Hauke is encountering an error during indexing with a specific field and working to provide Kishore Nallan with a reproducible example. Kishore Nallan gave troubleshooting advice, but issue not yet resolved.
1Issues with Semantic Search in OpenAI Embeddings
Semyon was having issues while creating a schema for semantic search with OpenAI embeddings. Jason gave multiple suggestions for troubleshooting but none of them worked. The error was narrowed down to possibly being related to Semyon's specific OpenAI account or the OpenAI API key. The thread ended with Jason suggesting Semyon to check billing and make a direct API call to OpenAI.
1Transitioning from Meilisearch to Typesense - Questions and Suggestions
Al is moving from Meilisearch to Typesense and asked for similar matching information features. They also proposed adding daily backups. Kishore Nallan helped them find a workaround, while noting expected complexities, and agreed to include their suggestions in their backlog.
3