At the moment, STRINGEQUALS with the case-insensitive flag requires a linear index scan over the property, so it is cardinality dependent, resulting in extremely high RU charges in large collections. Please implement a (perhaps optional) index that supports cardinality independent case-insensitive STRINGEQUALS. At the moment, the ugly workaround is to manually store duplicates of the property values in lower case. See also https://stackoverflow.com/questions/66024029/high-ru-charge-with-case-insensitive-search/66249495#662494959 votes
In some cases, string system functions may need to fall back to a scan. Adding an ORDER BY clause can help prevent this.
Please give this a try and let us know if this resolves the issue.
Group By should support cross-partition queries.13 votes
This is supported currently. In which SDK version do you not see this?
In a partitioned collection, it would be useful to have the option delete all data with a given partitionId.686 votes
We’re looking to get some feedback on this feature and would love for you to try out a preview.
- Don't see your idea?