Skip to content

Directly exporting "unreachable" sub-collections stopped working #73

@m417z

Description

@m417z

The issue is relevant to my previous issue here: #42

I previously reported that if I have a user whose document doesn't exist, but there is a sub-collection with documents, the sub-collection of this user is not exported.

You said that it wasn't possible to fix, so I wrote a script to do manual export per "unreachable" sub-collection, similar to:

const collectionRef = admin.firestore().collection('users/' + userId + '/semesters');
firestoreImportExport.firestoreExport(collectionRef).then(/*...*/);

It worked at least until a month ago. But today I discovered that it stopped working. And it seems that it stopped working only for such "unreachable" sub-collections, i.e. sub-collections that neither get exported via the full database export.

I understand that it's a regression on the Firestore end, but perhaps you have a workaround for this. If not, it would be great if you could send the Firestore team a report about this, or alternatively point me to the regressed API call and I'll try to contact them.

As of now, I don't have a way to do a full backup of my project's database, which kinda sucks :(

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions