Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I suggest that Firebase...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

115 results found

  1. Allow cross-project restoring of Firestore databases

    When working with Firestore databases, you may want to restore an entire database for testing in your stage project.

    However, currently, you can only restore in the same project

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  2. Improve firestore explorer UI - it is too small

    The UX when reading large objects in the firestore explorer UI requires too much scrolling in small windows to find the information you are after. I'd propose to:

    Note: "window" here refers to where the container where the data of a document can be found or alternatively where all the collection can be found. So the firestore explorer contains usually, a collection window, a document window, (a sub collections window, a document window,...).

    • collapse maps by default, or collapse maps if the object is larger than the current window. When dealing with large objects it's currently annoying to find the…
    7 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  3. Security Rules: unique() operator

    I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.

    Background:

    At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.

    Feature Proposal:

    The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed…

    25 votes
    3 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  4. Firestore: Use C++ implementation directly from Swift

    Swift has recently gained direct interoperability with C++.

    This would allow the current bridging layer written in Objective-C++ to be removed, which would in turn make it possible to use Firestore from Swift cross platform.

    The Browser Company have created patches for firebase-cpp-sdk to allow this:

    https://github.com/thebrowsercompany/swift-firebase

    It could also decrease the maintenance burden by removing the bridging layer code.

    3 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  5. 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.

    8 votes
    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?

  6. rules map

    In Firebase Firestore rules, we currently have various controls and functions, which are very handy. However, array management is not optimal. I propose introducing a map function for arrays in Firebase Firestore rules. This function would allow us to map arrays of objects, significantly simplifying the creation and management of rules.

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  7. Support deleting collections in the API

    Currently you can only delete collections programmatically via the CLI. Otherwise, you have to list and delete every single document in the collection. If those documents have nested collections, you have to (recursively) retrieve and delete every document in the nested collection (As deleting a document does not delete any nested collections the document has). If there are additional levels of nested collections... You get the idea.

    I wasn't sure what this other request was referring to so I made this one: https://firebase.uservoice.com/forums/948424-general/suggestions/46562317-api-support-for-deleting-directories

    8 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  8. Allow to assign tags to Firestore databases

    With multi-db support in Firestore now launched, this enabled many possibilities but also requires more granular inventory management of the databases created.

    --

    For compliance reasons and for better management of your cloud assets, it's important to assign metadata to your cloud resources.
    Especially for storage services, this is important, as it allows you to track which resources contain PII, who owns them, etc.

    --

    Attaching this kind of data is typically done using tags in Google Cloud.
    If it would be possible to attach tags to individual Firestore databases, this would solve the management of databases and allow easier…

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  9. Allow to attach IAM permissions to databases

    With multi-db support in Firestore now launched, this enabled a ton of new features, though the way permissions are granted is not ideal.

    --

    Instead of being able to attach permissions to individual databases, you have to use conditional IAM permissions on a project level.

    --

    This leads to problems when you want to grant IAM permissions to employees with access to only a subset of databases.
    Granting a subset of databases to access will prevent them from using the Firebase / Google Cloud console, as they will not have permission to view all databases.

    --

    Also conditional IAM permissions…

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  10. Support offset-based document access and pagination

    There should be an easy way to get a specific document by index in a query:

    // this query should work as it's read, if i wanted to use gte i'd use a where

    query(this.collection, orderBy('anything', 'asc'), startAt(index), limit(1))

    5 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  11. Expose createTime & updateTime in scheduled Firebase LevelDB exports

    I am using this procedure for regular backups: https://firebase.google.com/docs/firestore/solutions/schedule-export
    and some tooling to locally analyze data in the resulting (downloaded) LevelDB backups.

    The Admin SDK exposes (internally, but still) createTime, readTime and updateTime properties on snapshots. I don’t see these properties included in the database exports; which makes them less complete as backups, and less useful for data analysis.

    2 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  12. Orderby('any_potential_null_field', excludeNull: false) should exist

    OrderBy should be able to return collection item when target property is null.

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  13. provide feedback on database restore progress

    During a restore, there's no way to know how long it will take or where the progress is. It would be great to have some visibility into the process.

    I initiated a restore from a backup created by the automated schedules

    gcloud alpha firestore databases restore \
    --source-backup=projects/PROJECTID/locations/LOCATION/backups/BACKUPID \
    --destination-database='DATABASE_ID'

    I have seen this take between 20 minutes to over a day.

    The documentation for this feature is here:

    https://cloud.google.com/firestore/docs/backups

    2 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  14. Firestore : Throw error access data with offline cache without enable persistence

    When retrieving documents from Firebase's Firestore on the web, if you attempt to read the value from the cache, it will return an empty result.

    This seems to be an issue because Firestore's database does not use offline data when accessed from the web by default.

    To make developers aware of this, should throw some error if Firestore's database is set to not use offline data, and attempting to read the cache value.

    3 votes
    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?

  15. Duplicate document in collection in Firestore

    Duplicate document in collection in Firestore

    4 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  16. Ability to change project geographic location

    39 votes
    3 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  17. Request to Have a Firestore Profiler

    Similar to RTDB, it would be good to have a way to monitor Firestore usage as it happens. There are many reads happening that I would like to better understand the source of.

    38 votes
    2 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  18. Transactions should allow exponential backoff retries like pub sub

    Transactions allow passing an options object with maxRetries, but all retries are immediate. If there are many other functions writing the same document, transactions will fail after all retries (lock will time out). Maybe a better strategy would be to delay with exponential backoff like pub sub does.

    3 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  19. 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.

    10 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

  20. Implement rate limiting for read and write operations

    35 votes
    4 comments  ·  Firestore  ·  Admin →
    How important is this to you?
1 3 5 6
  • Don't see your idea?