microsoft / microsoft/vscode-documentdb

Future work: add MongoDB Atlas Search Index tab

Open
#815 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs-triage
Dominant language
TypeScript
Stars
31
Forks
22
Avg merge
2d 20h
Merged PRs (30d)
21

Description

Summary

Add a dedicated Search Index tab for MongoDB Atlas connections in Index Management.

PR #732 adds the Index Management experience and is currently focused on the Vector tab for Azure DocumentDB. Atlas uses a separate search index resource model and wire protocol commands, so it should have a separate Search Index tab rather than reuse the DocumentDB Vector tab.

Automatic provider based tab switching is not available yet. This issue tracks that switching behavior and the Atlas Search Index experience as future work.

Proposed scope

  • Detect when Index Management is connected to MongoDB Atlas.
  • Show a Search Index tab for Atlas instead of the Azure DocumentDB Vector tab.
  • Use createSearchIndexes, $listSearchIndexes, updateSearchIndex, dropSearchIndex, and $vectorSearch over the MongoDB wire protocol.
  • Preserve Atlas status and queryable as separate lifecycle values.
  • Support Atlas vector definitions, filter fields, indexing methods, and quantization through provider specific contracts.
  • Do not use the Atlas Administration REST API.

Context

Related PR: #732

The current implementation plan remains focused on Azure DocumentDB vector indexes. We will return to Atlas Search Index support and prioritize it based on customer requests.

Triage

This is future work and needs product and engineering triage.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing PR #732 and the existing Index Management experience, then identify where provider detection and the Azure DocumentDB Vector tab are handled. Done means Atlas connections show a separate Search Index tab using the listed MongoDB wire protocol commands, with the specified lifecycle and provider-specific index behavior; product and engineering triage is still needed first.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb, typescript
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.