#random

Transforming Firebase Collection Data before Indexing to Typesense

TLDR David wants to transform data before indexing to Typesense. Jason suggests forking the extension and using a Google Cloud function. David successfully implements the solution.

6mo

Join the chat

May 12, 2023 (7 months ago)

Photo of md5-7621a536ac5e9f5ac6d4713602bef5fd

David

12:52 AM

Hello again,

If I'm monitoring a firebase collection using the Typesense extension, is it possible to transform that data at all before it is indexed to Typesense? I want to add some more data to each record so I can filter on those values.

The values I want to add to each record are also the two fields in my Firestore Collection Path - pathOne/{thisValue}/pathTwo/{andThisValue}/pathThree - if I can't add them to a record using a firebase cloud function, can I filter on these values any other way?

Thanks 🙏

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

12:54 AM

This is not possible unfortunately. So you would have to fork the extension and run your own version of the cloud function provided by the extension

May 16, 2023 (7 months ago)

David

03:20 PM

Okay, unless there is some other configuration for filtering our data that we should explore, we may have to pursue this option..

Would it require publishing the forked version of the extension to the firebase extension marketplace? And has it been done before?

Jason

04:27 PM

You don’t have to publish it. You’d essentially take the code in this file and paste it inside a Google Cloud function inside your own project.

04:28

Jason

04:28 PM

> And has it been done before?
Yup, this is not an uncommon scenario.

Jun 05, 2023 (6 months ago)

David

06:08 PM

We've done this and everything has gone smoothly so far.

But does this also require a custom backfill function?

When backfilling data, we don't get any errors in the console, but the function runs and never enters the batching loops to write to typesense

06:16

David

06:16 PM

Nvm, think I answered my own question.. We need to modify typesenseDocumentFromSnapshot so the changes apply to both writing and backfilling..

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Resolving Issues with Firebase Extension and Typesense Configuration

Ernie sought clarification on how to handle the Firebase Extension and typesense collection configuration issues. Jason explained how to correctly specify the path and refresh the page to see updated data. After applying the advice given, Ernie successfully saw the changes.

15mo

Typesense and Firebase Integration Troubleshooting

Bobby struggled with getting data to Typesense from Firebase. After sharing his logs and settings screenshots, Jason helped him fix the path configuration and suggested ways to successful re-trigger a backfill. This resolved the issue.

21mo

User Queries About TypeSense Cloud and Firebase Integration

Loic had various queries about TypeSense Cloud and Firebase integration including modifying schema, existing documents, and geopoint and timestamp indexing. Kishore Nallan, Jason, and Harpreet provided clarifications and solutions.

27mo