Firestore to Typesense Backfill Issue with Dynamic Paths
TLDR Greg experienced issues with Firestore to Typesense backfill not working, and Jason determined it might be related to dynamic paths in Firestore collections not being supported. An RC version of the extension with dynamic path support was considered but needs further review before being shared with Greg.
1
Jun 07, 2023 (6 months ago)
Greg
04:56 PMJason
04:57 PMJason
04:58 PMGreg
05:11 PMGreg
05:18 PM“facet”: false,
“index”: true,
“infix”: false,
“locale”: “”,
“name”: “specs.dim_00”,
“optional”: true,
“sort”: false,
“type”: “float”
}, but it is showing int64 in the current schema. Maybe I messed up - I will try to recreate.
Greg
05:26 PMGreg
05:26 PM“created_at”: 1686158481,
“default_sorting_field”: “”,
“enable_nested_fields”: true,
“fields”: [
{
“facet”: false,
“index”: true,
“infix”: false,
“locale”: “”,
“name”: “user_ID”,
“optional”: false,
“sort”: false,
“type”: “string”
},
...
{
“facet”: false,
“index”: true,
“infix”: false,
“locale”: “”,
“name”: “specs.spec_00”,
“optional”: true,
“sort”: false,
“type”: “string”
},
...
{
“facet”: false,
“index”: true,
“infix”: false,
“locale”: “”,
“name”: “specs.dim_00",
“optional”: true,
“sort”: false,
“type”: “float”
},
...
],
“name”: “collectibles”,
“num_documents”: 0,
“symbols_to_index”: [
“+”,
“-”
],
“token_separators”: []
}
Greg
05:35 PMGreg
05:38 PMGreg
05:40 PMJason
05:44 PMJason
05:45 PMGreg
05:47 PMJason
05:49 PMuid
could you try using an actual uid in the collection name in the typesense_sync collection to see if that works?Jason
05:50 PMGreg
05:51 PMJason
05:53 PMGreg
05:55 PMJason
05:56 PMGreg
05:57 PM1
Jason
05:58 PMGreg
05:58 PMJason
07:32 PMGreg
07:40 PMGreg
07:42 PMJason
07:44 PMobject
, then any new fields you add inside the object will get auto-added to the schema as they’re encountered in new documentsJason
07:45 PMGreg
08:21 PMJason
08:23 PMIs this a completely different field? or did you mean that you’re now adding the parent key to the schema as an
object
type?Jason
08:24 PMGreg
08:24 PMJason
08:24 PMobject
all subfields, new and old will get added to the schema and indexedJason
08:25 PMGreg
08:26 PMJason
08:26 PMTypesense
Indexed 3011 threads (79% resolved)
Similar Threads
Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.
Cold Start Problem with Dynamic Collections
Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.
Specific Collection Backfill and Schema Config in Firebase Extension
Loic asked Jason about backfilling specific collections with the Firebase Extension and configuring collection schemas. The latter explained current limitations and gave advices about handling attributes for search/filtering, storage, and return.
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.
Nested Objects Issue in Firebase & Typesense Integration
Shaun encountered issues with nested objects being flattened in Typesense. Jason found the root issue and provided a solution involving updating the Firebase extension to 1.0.3.