DOCSP-32634: Add Indexes page #206
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jordan-smith721
requested changes
Jun 4, 2024
JamesKovacs
suggested changes
Jun 12, 2024
mcmorisi
commented
Jun 12, 2024
| Console.WriteLine("wildcard index"); | ||
|
|
||
| // begin-wildcard-index | ||
| collection.Indexes.CreateOne(Builders<Theater>.IndexKeys.Ascending("location.$**")); |
There was a problem hiding this comment.
@JamesKovacs Wanted to specifically draw your attention here – is this the preferred way to implement an ascending wildcard index using the Builders model?
There was a problem hiding this comment.
We have a Wildcard method on IndexKeys.
coll.Indexes.CreateOne(
new CreateIndexModel<Theater>(Builders<Review>.IndexKeys.Wildcard(x => x.Location))
);
There was a problem hiding this comment.
In this case, would the x.Location wildcard be defined in the Theater Poco as something like this?
[BsonElement("location.$**")]
public string LocationGeo { get; set; }
There was a problem hiding this comment.
[BsonElement] specifies the field name in the database and is unrelated to wildcard indexes. You would still specify this field as location.geo.
JamesKovacs
suggested changes
Jun 12, 2024
| Console.WriteLine("wildcard index"); | ||
|
|
||
| // begin-wildcard-index | ||
| collection.Indexes.CreateOne(Builders<Theater>.IndexKeys.Ascending("location.$**")); |
There was a problem hiding this comment.
We have a Wildcard method on IndexKeys.
coll.Indexes.CreateOne(
new CreateIndexModel<Theater>(Builders<Review>.IndexKeys.Wildcard(x => x.Location))
);
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mcmorisi
added a commit
that referenced
this pull request
Jun 17, 2024
(cherry picked from commit d150844)
mongoKart
pushed a commit
to mongoKart/docs-csharp
that referenced
this pull request
May 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Info
PR Reviewing Guidelines
JIRA - DOCSP-32634
Staging - https://preview-mongodbmcmorisi.gatsbyjs.io/csharp/DOCSP-32634-indexes/fundamentals/indexes/
Self-Review Checklist