diff options
| author | Drew Paroski <drew.paroski@mongodb.com> | 2022-09-13 14:55:15 +0000 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2022-09-13 16:03:14 +0000 |
| commit | 85ec8439047fae7c337501987a38ef97a7596e0f (patch) | |
| tree | ec890e9b888d95d2770d965f4672b1517ed04941 | |
| parent | 46ba973f76d101f74769619d4fe48d9522c3969c (diff) | |
| download | mongo-85ec8439047fae7c337501987a38ef97a7596e0f.tar.gz | |
SERVER-69605 Complete TODO listed in SERVER-59757
| -rw-r--r-- | src/mongo/db/matcher/expression_parser.cpp | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/mongo/db/matcher/expression_parser.cpp b/src/mongo/db/matcher/expression_parser.cpp index f4ae7fc5168..a0f3d0d256a 100644 --- a/src/mongo/db/matcher/expression_parser.cpp +++ b/src/mongo/db/matcher/expression_parser.cpp @@ -93,10 +93,6 @@ bool hasNode(const MatchExpression* root, MatchExpression::MatchType type) { // TODO SERVER-49852: Currently SBE cannot handle match expressions with numeric path // components due to some of the complexity around how arrays are handled. -// -// TODO SERVER-59757: We also currently fall back to classic engine when encountering match -// expressions on empty field names due to complexity in how an empty string currently has -// multiple special meanings & which we do not wish to emulate in SBE. void disableSBEForUnsupportedExpressions(const boost::intrusive_ptr<ExpressionContext>& expCtx, const MatchExpression* node) { auto fieldRef = node->fieldRef(); |