-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple inequality support #7453
Conversation
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1This report is too large (443,647 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
b77a49c
to
9d6ab9f
Compare
9d6ab9f
to
bceea26
Compare
Multiple inequality support
Firestore is removing the following restrictions around inequality filters (<, >, <=, >=, !=, not-in):
But the limitation on
!=
andnot-in
remains the same, which is, at most one!=
orNOT_IN
filters allowed in a query.Ordering:
Firestore SDK normalizes the orders in a query by following rules:
Note that if there's an explicit orderBy on document key, therefore it's not the last one in order, there will be an error from the backend. The SDK will not perform this validation.
Client side indexing
This PR doesn't update the client side indexing. So the limitations above (single inequality, first order by field match) remains in this matter. When there is multiple inequality, it simply skips client side indexing.