"Google has overhauled Firestore Enterprise edition's query engine, adding Pipeline operations that let developers chain together multiple query stages for complex aggregations, array operations, and regex matching. The update removes Firestore's longstanding query limitations and makes indexes optional, putting the database on par with other major NoSQL platforms. Pipeline operations work through sequential stages that transform data inside the database."
"The Firebase team illustrated the change with a recipe app example. Previously, if tags were stored as arrays within recipe documents, there was no way to extract and count them within a query to find trending tags. Developers had to maintain separate tag metadata. With Pipeline operations, a single query can unnest the tag array, count occurrences across all recipes, group by tag name, sort by popularity, and return the top ten."
Google overhauled Firestore Enterprise's query engine to add Pipeline operations that chain multiple query stages for complex aggregations, array operations, and regex matching. Pipeline stages can unnest arrays, aggregate results, and filter on aggregation outputs, enabling queries previously impossible without separate metadata. The new engine supports over 100 query features and is available in preview for Android, iOS, web, and admin SDKs, with Flutter, Unity, and C++ support coming later. A recipe example demonstrates unnesting tag arrays, counting occurrences, grouping by tag, sorting by popularity, and returning top results. Enterprise edition no longer requires automatic single-field indexes.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]