79 results found
-
Move documents and collections to a new location
Instead of making us create inefficient solutions/workarounds ourselves, it would be nice if a convenient API was provided for this functionality.
For example, transfer
col1/doc1/col2and all its children tocol1/doc2/col28 votes -
Allow field selections in client sdk's
Let's say I have an orders collection where each document represents a customer order.
I would like to be able to fetch and listen to only the names and dates of all orders and not get the whole document.
This would speed up a lot queries where not all fields are required and save bandwidth for users.
Since selection is already present in some server side SDK's I wonder if this could be enabled with a somewhat manageable effort.
8 votes -
Firestore Index Name
As a Firestore project grows, so do the number of Composite Indexes.
While the fields are visible, being able to name a composite index would allow us to define which specific feature(s) a composite index is tied to, allowing us to remove unused indexes if they're no longer relevant.
8 votes -
Firestore return document when it gets updated
As we get the whole document when it is created, it would be nice to get it as well when it gets updated.
Example:
Online game where 4 people join together. In document, we have a list of players with their names. These names should be displayed for all players. Last user joins closing the session. To get the rest of the names after update the document with this last player, I need to do an extra read.Problem:
I am making an entra call for every player, affecting my quota limitation.Solution:
Return updated document.7 votes -
Ability to disable deleting collections and documents from firebase console
In Firebase's Firestore, a user with write access to a project can simply delete any document and even a whole collection with multiple documents with a single click. This is a major security problem as any of my team member may end up deleting a whole collection with millions of documents in under a minute, through the Firebase console.
I would like to request for a feature to disable this.
To be clear - The possibility to grant write access without delete access. Currently, if I am not mistaken, through the User and Permissions panel it's kind of "all or…
7 votes -
Expose "last updated" metadata
If Firebase cannot support some kind of changestream implementation, it should include metadata on each document that includes a "last updated" timestamp. Then clients can query against this field to only retrieve "new" changes (Inserts, Updates). It lacks support for delete capture but is the next best thing after a changestream.
7 votes -
Firestore insights dashboard
Same dashboard in GCP as Firestore in datastore mode. Collection storage space usage, index size, data size, etc.
Also, for multi tenancy apps in both modes (using subcollections or multiple databases or also schemas in native mode would be nice to have) an API that can tell how much resources - space, reads, writes, etc. did each customer use, to be able to offer some kind of pay-as-you-go type of subscription.
7 votes -
Firestore Blocking Functions
Blocking functions for Firestore e.g. block writing a document until a certain condition is met
7 votes -
7 votes
-
Changestream
Firestore does not support any actual CDC (Change Data Capture). A changestream similar to other NoSQL implementations (Mongo, DocumentDB, Azure Cosmos DB) would make the database a lot more usable and grant feature parity with other popular NoSQL databases. This changestream would expose operations like updates, inserts, and deletes for a client to come and retrieve from either a timestamp or a resume token.
6 votes -
6 votes
-
Join collections in real-time (similar to lookup in mongodb)
The ability to join collections in real-time really allows developers to build complex use cases. Currently, I am having to denormalize data so excessively that the solution doesn't seem to scale. Having to implement workaround after workaround to circumvent the limitations.
An aggregate lookup function similar to that of mongodb would really be a life save. We are ok to compromise on the extra reads, and some performance if it means to bring us data consistency.
Really having this feature would stop people looking into RDBMS based alternative such as Supabase.
6 votes -
Feature like RELATE statements
A RELATE statement to adds graph edges between records. Like the convention of vertex -> edge -> vertex or noun -> verb -> noun, enabling the addition of metadata to the edge record.
6 votes -
Improve performance & speed of client side write
I've used both Firestore and MongoDB's Realm Device Sync. While Firestore works great in terms of scaling, the performance and speed for client side write is far behind realm, especially when client side is doing some batch writes.
Realm uses techniques like data compression and delta sync to reduce the data size when uploading (https://www.mongodb.com/docs/atlas/app-services/sync/details/protocol/), I'd like to see Firestore doing the same and improve the performance of client side batch write.
Also, what I've noticed is that Firestore's client side write performance degrades a lot after some time being offline, this isn't great for apps that would…
5 votes -
Support array-contains-prefix operator in Firestore
You can build a search index in a Firestore collection by storing an array of search words.
If you query this property using 'array_contains' you get exact matches for your search string.
If you wish to build a prefix search, then you potentially need to store all prefixes of the words you need to index.Assuming that the array-contains is performing some kind of index scan, it would appear that it was possible to create an array-contains-prefix such that:
where('index', 'array-contains-prefix', 'fire')
would match the following documents[
{ index: ["firestore", "database"],
...
},
{ index: ["firebase", "dog"],
...
}…
5 votes -
Rules between Firestore and Realtime Database
We've rules to limit access to data in both firestore and realtime database, but there are requirements where I need to specify a rule of realtime database based on a value in Firestore.
Games are classical examples, I want to store the realtime game data in realtime DB but apply rules to read and write there based on my user and app data in firestore.
Lack of this is either making me use either of the DB or write hard rules in client side (which is not really secure).
5 votes -
Encrypted Collections in Firestore
Ability to mark certain collections to be Encrypted so it's not readable even in the firebase console.
There are some application types that require this sort of behaviour to increase security.
Say you are building a messaging app, you would not want the messages between your users to be seen on the console.
4 votes -
The ability too see when an index was last accessed
When a project grows to a certain size, you'll likely have many indexes with associated queries.
However, queries change, or get removed, and currently there's no way to see if an index could be safely removed, after a query is; which would be a great feature.
4 votes -
Ability to select and copy fields and values in firestore document
Ability to select and copy fields and values in firestore document, more like making everything selectable text.
4 votes -
Wildcard index exemptions
Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.
We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.
In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.
It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.
We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index…
4 votes
- Don't see your idea?