[nerdywordy]

Anyone with inside knowledge of Firestore care to comment on the ETA of more advanced query functionality?

We have played with Firestore quite a bit, but rely heavily on the ability to do aggregate queries. Reading all of the documents and performing this on the client side is nowhere near good enough. Nor is triggering functions to update a "count" or "sum" property on a doc.

Edit: Looks like a PM answered on another thread...

"It's a point of internal discussion on scalable ways to achieve this, but nothing we can promise. We definitely see the need for it."

[doczoidberg]

Firestore is very limited here. I trigger a cloud function on every new entry and replicate my data in bigquery. This solves the problem for me.

[pier25]

Firestore was a big disappointment for me.

By far the biggest pain point of the RTDB was its poor querying capabilities. Firestore solved some of those problems, but it's still very limited.

We moved away from Firebase primarily because of the serious limitations of the 2 DBs.

[asien]

The documentation clearly mention those features aren’t supported as of now.

The Firebase team is aware of that need but it’s very hard to deliver such features at scale.

Firebase is used everywhere these days , so a single change in the platform has impacts in petabytes and massive thousands of cpus load.

[nerdywordy]

I get that it isn't supported. We have followed the recommendations mentioned in the docs but found the usage of these workarounds to be sorely lacking in performance and reliability.