@rsun11 if you have the time to create a PR, I can review it. I am going to do some investigation on this.

Tried deploying the same code to a gen 2 trigger but the database context is referencing the default database so “exists” property always returned false and calls to the named database throws an exception.

@rsun11 can you share your configuration? the Firebase team has not heard of this issue so they are wondering if the extension was misconfigured.

entered:

• extension instance ID: nucleus-70fd6e56-973f-4436-b650-dc308ddc9b2a
• Database ID: nucleus-70fd6e56-973f-4436-b650-dc308ddc9b2a
• collection path: products
• Force Data Sync: no
• algolia index name
• algolia application id
• full index existing documents: false
• cloud functions location: us-west3

Tried again this morning and the same issue is happening...

Finally got the trigger to work with:

export const executeIndexOperation = onDocumentWritten( { document: 'documents/{documentId}', database: DATABASEID, region: REGION, }, async (change): Promise<void> => {

but this only works when deployed using the firebase cli.

• if you manually create a new gen 2 trigger with the code above, a byte array is passed to the function
• if you deploy the trigger with gcloud cli, a byte array is passed to the function
  the byte array will need to be processed like this: https://cloud.google.com/functions/docs/calling/cloud-firestore

Also, executeFullIndexOperation wasn't working with a named database. The query would always return results from the default database. Had to update to:

    "firebase-admin": "^12.0.0",
    "firebase-functions": "^4.8.2",

for it to start working again.

hey @rsun11 I am going through the updates you mentioned here. I am also talking to the Firebase team which seems surprised that I had this working in gen1 before some update that broke it. will let you know what happens.

One thing to try would be to deploy the current code as a gen 2 trigger but with the firebase package updates from above.

hey @rsun11

I tried implementing you suggestions. using the CLI deploy the update code, fails with this error message:

- update firestore-algolia-search-s4eg
; RESOURCE_ERROR at /deployments/firebase-ext-firestore-algolia-search-s4eg/resources/executeIndexOperation: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"400","ResourceErrorMessage":"Cannot create Firestore trigger for projects/algolia-store/databases/test. Triggers must be created with a \"(default)\" Firestore Native database. See https://firebase.google.com/docs/firestore/extend-with-functions#limitations."}

What steps did you take to implement gen2 versions for the extension.

If you change the function to

export const executeIndexOperation = onDocumentWritten( { document: 'documents/{documentId}', database: DATABASEID, region: REGION, }, async (change): Promise<void> => {

the deployment will detect the signature as gen 2. I don’t think DatabaseId, document path, and region could not be stored as environment variables since the deployment needs those values populated during deployment to create the trigger.

hey @rsun11 I am working with the firebase team to see if we can get this resolved. No eta at the moment.

hey @rsun11 is this still an issue?