It seems like when the amount of data gets too large, Firebase goes into a "Read-only & Non-realtime Mode" which they didn't warn about. In this mode, the Export JSON does not work. I can go into each and every node to extract the JSON, but that will mean that I have to do for tens of nodes. How do I get the node (that is currently too large) to become real time again, or how do I export the JSON when it is non-realtime? Also, is Firebase still writable when it is in non-realtime?
3 Answers
I'm just face the problem that user8267710 mention above. In my case (and I guess in Bob Snyder's) the problem only appears when you try to download the JSON from root, i.e. "/", the upper level.
I'm had success to download the full database tampering the download url. When I tried to download from root the fail url is something like:
https://example.firebaseio.com/.json?print=pretty&format=export&download=example-export.json&auth=eyJhb...
If you change it adding a "/" before ".json" immediate after the db name, the link works as desired and all the data is downloaded ( at least in my case :-). In the example case is:
https://example.firebaseio.com//.json?print=pretty&format=export&download=example-export.json&auth=eyJhb...
God Luck!
Yes, the console will stop reflecting updates to data in real time when your data set becomes too large. If you need to download parts of your database outside the console, you can still use the REST API to download any or all of your database.
Try checking the status of your application under https://console.cloud.google.com/appengine/settings.
I was playing around with the Google Cloud Platform, and ended up disabling the App Engine. After enabling it again, Firebase Realtime Database's "Export JSON" function started working again instantly.
https://onyx-segment-999.firebaseio.com/.json?print=pretty&format=export&download=onyx-segment-770-export.json&auth=eyJAhR...IBQAYmight be temporarily down or it may have moved permanently to a new web address. - Bob Snyder