Allow indexing and querying for null datatype in Atlas Search
The null datatype is not amongst the datatypes that Atlas Search supports at this time. As a result, if the use-case is to perform a text search on some fields and perform an equality/inequality check on other field(s) to see if it is/isn't null, then we need to have a $match stage following the $search stage, which is detrimental to the query performance as documented here. This is an enhancement request to allow indexing and querying for null datatype in Atlas Search, to avoid the above scenario.
Harshad
shared this idea
This work is now complete. Update your search index to search for null using the Atlas Search equals operator on any field that is statically or dynamically indexed.
-
Sai Srinivasan
commented
This feature is critical to our workflows of being able to filter under multiple criteria without performance setbacks. We'd love to have most of our filtering conditions happening through atlas search.
-
Matt
commented
Lack of this feature is preventing us for adopting Atlas Search
-
Prasad Kini
commented
Hello,
Are there any plans to include this important feature in Atlas search?Thanks,
Prasad -
pawan
commented
This is a must which should be taken into consideration as a high priority. The $match impacts performance and using a combination/hacks of must, mustNot, range, equals make the query so ugly that it impacts the performance of person writing it.
-
Ramesh
commented
Null check filter is important. We are struggling to get some Mongo filters working on AtlasSearch without this. Hope to see this feature coming to AtlasSearch soon.
-
Dustin
commented
This would be extremely helpful for fields that can either NOT exist or exist but be NULL. This feature would allow us to avoid using a $match aggregation stage after our $search.