RI-8171 Create index when no data exists

[dantovska]

What

Allows the Vector Search create-index wizard to be used on databases with no Hash/JSON keys:

• The welcome screen button is renamed to "Create index" and is always enabled; same for the list page's "Use existing data" menu item (the "no keys" disabled guards are removed).
• When the database has no Hash/JSON keys, the "Select key" browser panel is hidden and the index definition panel switches to manual creation: centered guidance, "+ Add field", editable index name and prefix, and a HASH/JSON key type toggle (nothing else can set the type when no key is selected). The Command view renders (empty) even before the first field is added.
• Hardens the existing-keys probe (useHasExistingKeys), since the page layout now depends on it:
  • scans with SCAN_COUNT_DEFAULT instead of count: 1, scanThreshold: 1, which gave up after a single scanned key — false "no keys" whenever a non-Hash/JSON key came first in scan order, and key-by-key round trips;
  • aggregates results across all cluster nodes — previously only data[0] was read, so keys living on any other shard made the wizard claim the database was empty;
  • a failed probe falls back to browse mode instead of hiding the browser;
  • an incomplete scan (threshold reached without finding keys) is treated as inconclusive and also falls back to browse mode — manual creation only appears for a confirmed empty scan;
  • runs once per create-index page visit, and only for the browse flow (sample-data and preselected-key URLs never fire the scans; other Search routes no longer consume it).
• New/changed strings go through i18n (en + bg).

Notes for review: the prefix is optional in manual mode to match the browse flow (an empty prefix indexes all keys of the selected type), and manual creations report the same data_source: existingData telemetry as the browse flow.

Testing

• Unit: vector-search suites pass (77 suites / 731 tests), including new cases for manual mode (browser hidden, guidance text, create enabled after adding a field, chosen key type in the generated command, empty command view, loader while checking keys) and for the probe (multi-node cluster response, API error fallback, default scan count, silent re-checks).
• Manual (standalone): on a DB without Hash/JSON keys — Search → Create index → manual mode; add a field, pick key type → Create → FT.CREATE succeeds and lands on the query page. On a DB with hash keys — the key browser flow is unchanged.

Testing the cluster edge case (keys on a non-first shard)

The keys endpoint returns one scan result per cluster node; before this PR the probe read only the first entry, so keys on any other shard showed manual creation instead of the key browser.

1. Start a 3-master cluster with search modules (single container so the cluster bus works on macOS):

   docker run -d --name redis-cluster-search \
     -p 7101-7103:7101-7103 -p 17101-17103:17101-17103 \
     redis/redis-stack-server:latest bash -c '
       for port in 7101 7102 7103; do
         redis-server --port $port --cluster-enabled yes \
           --cluster-config-file /tmp/nodes-$port.conf \
           --cluster-announce-ip 127.0.0.1 --protected-mode no --daemonize yes \
           --loadmodule /opt/redis-stack/lib/redisearch.so \
           --loadmodule /opt/redis-stack/lib/rejson.so
       done
       sleep 3
       redis-cli -p 7101 --cluster create 127.0.0.1:7101 127.0.0.1:7102 127.0.0.1:7103 \
         --cluster-replicas 0 --cluster-yes
       tail -f /dev/null'

   (The plain redis Docker images ship without the search module — redis/redis-stack-server is required.)
2. Add 127.0.0.1:7101 to RedisInsight — it auto-discovers as an OSS Cluster.
3. Seed exactly one hash key; the {N} hashtag controls which shard it lands on:

   docker exec redis-cluster-search redis-cli -c -p 7101 HSET 'user:{1}' name test

4. Search tab → Create index: the "Select key" browser must appear and list the key. Repeat for other placements (DEL the key, reseed as user:{2}, user:{3}, user:{4}) — every placement must show the browser. Before the fix, keys on non-first response nodes (discovery order, not slot order) produced manual creation instead.
5. Cleanup: docker rm -f redis-cluster-search.

---

Closes #RI-8171

🤖 Generated with Claude Code

---

Note

Medium Risk
Layout and FT.CREATE inputs now depend on a hardened keys scan (cluster/incomplete-scan edge cases); wrong probe results could show manual vs browse incorrectly, but failures intentionally fall back to browse mode.

Overview
Enables Vector Search index creation when a database has no Hash/JSON keys, instead of blocking entry with “no keys” tooltips and disabled actions.

Entry points: The welcome secondary action and list Use existing data are always available and relabeled to Create index; global hasExistingKeys gating is removed from VectorSearchProvider, welcome screen, and create menu.

Create-index page: On browse (?mode=existingData without a preselected key), useHasExistingKeys runs once (with a loader). A confirmed empty scan switches to manual creation: hide the key browser, show manual empty-state copy, allow + Add field, index name/prefix editing, and a HASH/JSON key-type toggle; create is enabled with at least one field (no key selection). Probe errors or inconclusive scans (incomplete cursor) keep browse mode with the browser visible.

useHasExistingKeys: Scans use SCAN_COUNT_DEFAULT, aggregate all cluster nodes, treat non-zero cursor as “has keys,” expose error and an enabled flag; the hook is no longer used app-wide for disabling UI.

i18n updates in en and bg; unit/e2e tests cover manual mode and probe behavior.

^{Reviewed by Cursor Bugbot for commit 96f8b9d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e1813fa1a5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[github-actions]

Code Coverage - Frontend unit tests

St.❔	Category	Percentage	Covered / Total
🟢	Statements	84.03%	27249/32428
🟡	Branches	70.06%	11653/16632
🟡	Functions	79.43%	7302/9193
🟢	Lines	84.5%	26534/31402

Test suite run success

7769 tests passing in 860 suites.

Report generated by 🧪jest coverage report action from 96f8b9d

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a4336a2807

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c46018a60

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 44b7cd2d09

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 63150970f0

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eeba2f78a3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eb1478c018

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5ea9df719c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 96f8b9d. Configure here.}