You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`in` - Multiple value exact matching (string fields only)
644
644
-`like` - Case-sensitive wildcard matching
645
645
-`ilike` - Case-insensitive wildcard matching
646
646
-`gt` - Greater than (lexicographic comparison for strings)
@@ -696,17 +696,12 @@ To support `like` and `ilike` operators with proper case sensitivity handling, y
696
696
{
697
697
"type": "token"
698
698
}
699
-
],
700
-
"id": {
701
-
"type": "token"
702
-
}
699
+
]
703
700
}
704
701
}
705
702
}
706
703
```
707
704
708
-
**Note on UUID Fields**: MongoDB Atlas Search (cloud) supports a dedicated `uuid` field type, but `token` type works for UUID string values in both Atlas Search and MongoDB Community Search editions. The query builder treats both the same way.
709
-
710
705
**Query Builder Configuration:**
711
706
712
707
The `FieldToMultiAnalyzers` map specifies which multi-analyzer to use for each field:
@@ -728,15 +723,15 @@ This allows you to mix fields with and without multi-analyzer support in the sam
728
723
##### Limitations
729
724
730
725
1. The following operators are not yet implemented: `contains`, `contains_any`, `contains_all`, `is_null`
731
-
2. Range operators (`gt`, `ge`, `lt`, `le`) perform lexicographic comparison on string fields. For numeric comparisons, ensure fields are indexed with appropriate numeric types
732
-
3. Atlas Search requires proper [search index configuration](https://www.mongodb.com/docs/atlas/atlas-search/create-index/) with appropriate field types:
726
+
2. The following field types are not currently supported: UUID fields, Date fields, Numeric fields (numbers are compared as strings)
727
+
3. Range operators (`gt`, `ge`, `lt`, `le`) perform lexicographic comparison on string fields only
728
+
4. Atlas Search requires proper [search index configuration](https://www.mongodb.com/docs/atlas/atlas-search/create-index/) with appropriate field types:
733
729
- String fields used with `like`/`ilike` should be indexed with multi-analyzers as shown above
734
730
- String fields used with `eq`/`in` should be indexed with `token` type
735
731
- String fields used with range operators (`gt`/`ge`/`lt`/`le`) work with `token` type for lexicographic comparison
736
-
- UUID fields should be indexed with `token` type
737
732
- Text fields should be indexed with `string` type and an appropriate analyzer
738
-
4. Unlike regular MongoDB queries, Atlas Search queries use the aggregation pipeline with the `$search` stage
739
-
5. Additional filters (like tenant boundaries) should be added as separate `$match` stages in the pipeline
733
+
5. Unlike regular MongoDB queries, Atlas Search queries use the aggregation pipeline with the `$search` stage
734
+
6. Additional filters (like tenant boundaries) should be added as separate `$match` stages in the pipeline
0 commit comments