This message was deleted.
# community-help
s
This message was deleted.
j
Could you share a screenshot of your Search Parameters settings and/or Presets
t
CleanShot 2025-06-05 at 09.26.09.png
j
And also the search bar together with the search results? Your earlier screenshot only showed the search results
t
sec
im on typesense version 28.0 running on cloud if that matters
wait sorry, that's the wrong preset, let me do that again.
Take 2:
j
@Alan Martini ^
👀 1
t
Hey @Jason Bosco how can I follow this for updates? It's impacting our end users so we want to make sure we can apply a fix as soon as we can
a
Hey @Ted Mader, I tried replicating the issue using the script below, but I wasn't able to reproduce it—the returned text match scores are identical. Would it be okay for us to clone your cluster into our internal debugging environment to investigate further? We will make sure to delete all data after it. For reference, here’s the script we used (we also tried using presets, but the results were the same):
Copy code
#!/bin/bash

### Run Typesense via Docker ########################################
export TYPESENSE_API_KEY=xyz
export TYPESENSE_HOST=http://localhost:8108
export TYPESENSE_PORT=8108

docker stop typesense-repro 2>/dev/null
docker rm typesense-repro 2>/dev/null
rm -rf "$(pwd)"/typesense-data-dir-repro
mkdir "$(pwd)"/typesense-data-dir-repro

# Wait for Typesense to be ready
docker run -d -p $TYPESENSE_PORT:8108 --name typesense-repro \
            -v"$(pwd)"/typesense-data-dir-repro:/data \
            typesense/typesense:28.0 \
            --data-dir /data \
            --api-key=$TYPESENSE_API_KEY \
            --enable-cors

# Wait till typesense is ready
until curl -s -o /dev/null -w "%{http_code}" "$TYPESENSE_HOST/health" -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" | grep -q "200"; do
  sleep 2
done


# Create collection
curl -X POST "$TYPESENSE_HOST/collections" \
  -H "Content-Type: application/json" \
  -H "X-TYPESENSE-API-KEY: xyz" \
  -d '{
    "name": "YOUR_COLLECTION_NAME",
    "fields": [
      {"name": "shortId",   "type": "string"},
      {"name": "keywords",  "type": "string[]"},
      {"name": "topics",    "type": "string[]"},
      {"name": "popularity","type": "int32"}
    ],
    "default_sorting_field": "popularity"
  }'


curl -X POST "$TYPESENSE_HOST/collections/YOUR_COLLECTION_NAME/documents" \
  -H "Content-Type: application/json" \
  -H "X-TYPESENSE-API-KEY: xyz" \
  -d '{
    "keywords": [
      "Nicks - Robert",
      "Nicks Handmade Boots",
      "Nicks - 55",
      "Horween Brown Chromexcel",
      "Vibram 700 Tygum V-Bar Full Sole Black"
    ],
    "popularity": 8,
    "shortId": "QiLfeyT",
    "topics": [
      "6803c819a132f6c950755d9c",
      "68028873903fc39d877489dd",
      "6805143d7922e4b1753037f7",
      "6803cd4ee5c82c92a297bfc8",
      "6803d1232b25930a6c35e417"
    ]
  }'


curl -X POST "$TYPESENSE_HOST/collections/YOUR_COLLECTION_NAME/documents" \
  -H "Content-Type: application/json" \
  -H "X-TYPESENSE-API-KEY: xyz" \
  -d '{
    "keywords": [
      "John Lofgren Bootmaker",
      "John Lofgren - Combat Boots",
      "Horween Black Chromexcel",
      "Vibram 7335 Cork Heel",
      "John Lofgren - 120",
      "Vibram 700 Tygum V-Bar Full Sole Brown Cork"
    ],
    "popularity": 5,
    "shortId": "HHEM8Bx",
    "topics": [
      "68028873903fc39d87748973",
      "6803c805a132f6c9507541d4",
      "6803cd4ee5c82c92a297bf8f",
      "6805143c7922e4b175303752",
      "6803d1232b25930a6c35e39f"
    ]
  }'


RESULT=$(curl -X POST "$TYPESENSE_HOST/multi_search" \
  -H "Content-Type: application/json" \
  -H "X-TYPESENSE-API-KEY: xyz" \
  -d '{
        "searches": [
            {
                "query_by": "keywords",
                "sort_by": "popularity:desc",
                "per_page": 6,
                "highlight_full_fields": "keywords",
                "collection": "YOUR_COLLECTION_NAME",
                "q": "Brown Chromexcel",
                "page": 1
            }
        ]
    }' | jq .)

echo $RESULT | jq .

docker stop typesense-repro
docker rm typesense-repro
t
Hey @Alan Martini you can go ahead clone our cluster. thanks!
Hey @Alan Martini is there any news about this? This is still impacting our users. Hoping it is something we can tweak on our end or work around!
a
Hi @Ted Mader, I've checked internaly but, unfortunately, we don't have an estimated time yet. It is requiring a deeper, thorough investigation, which is quite time-consuming. Will be back at you as soon as we have any news.
t
Sure thing! Let me know if there's anything on my end I can do to work around the issue