Discussing Firestore Extension and Collection Schema in Typesense
TLDR Loic asks about settings in Firestore Extension and experiences issues with the collection schema in Typesense. Discussion with Jason is ongoing.
1Aug 30, 2023 (1 month ago)
Loic
11:18 PMIn Firesbase Extension, the doc says to set "Yes" in both cases, is this normal?
Adds a new parameter that controls whether a nested Firestore document is flattened by the extension, or sent as is to Typesense.
If you are running Typesense Server v0.23.1 or below, set "Flatten Nested Documents" to "Yes" (since indexing nested fields is not supported in these versions).
If you are running Typesense Server v0.24 or above, set "Flatten Nested Documents" to "Yes" (since indexing nested fields is natively supported in Typesense in these versions).
Jason
11:19 PMI did fix the typo in the changelog here: https://github.com/typesense/firestore-typesense-search/blob/master/CHANGELOG.md#version-100
Loic
11:20 PM
Jason
11:21 PMLoic
11:23 PM1Sep 06, 2023 (3 weeks ago)
Loic
04:09 PMI have a problem with my collection schema.
I have a class as below:
Loic
04:09 PMclass Temperatures {
String brokerId;
List<PickedProduct> pickedProduct;
Temperatures({
required this.brokerId,
required this.pickedProduct,
});
}
class PickedProduct {
String uniqueTicker;
int brokerRetailPrice;
String brokerCurrency;
String brokerDescription;
bool showOriginalPictures;
bool showGenericPictureFirst;
PickedProduct({
required this.uniqueTicker,
required this.brokerRetailPrice,
required this.brokerCurrency,
required this.brokerDescription,
required this.showOriginalPictures,
required this.showGenericPictureFirst,
});
}Loic
04:09 PMLoic
04:09 PM{
"brokerId": "abc",
"pickedProduct": [
{
"uniqueTicker" : "abc",
"brokerRetailPrice" : 100,
"brokerCurrency" : "abc",
"brokerDescription" : "abc",
"showOriginalPictures" : true,
"showGenericPictureFirst" : true
}
]
}Loic
04:10 PMLoic
04:10 PMJason
04:55 PMobject[] would indeed be the way to store that object, since it's an array of objects. Could you elaborate on why it's not a good solution?
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Issue with "Search Firestore with Typesense" Extension
Rajbek had an issue synchronizing data between Firestore and Typesense collection. Jason helped diagnose the issue and the problem was resolved by Rajbek increasing the memory allocation of the specific cloud function.
2Issue with Embedding Error in Version 0.25.0.rc63
Bill reported a bug in version 0.25.0.rc63 regarding a problem with updating or emplacing a document and receiving an embedding error. This was resolved in version 0.25.0.rc65, but further discussion ensued regarding the function of 'index' in the update feature.
5Resolving Issues While Upgrading Typesense Server
Ayush had queries about upgrading their Typesense server and updating collections using auto-embeddings. Kishore Nallan clarified all issues, but later discovered that reindexing of non auto-embedded vector fields only is currently supported during altering.
Issue with Enabling Nested Fields in Existing Collection
Manish had issues querying a nested field 'bits' after changing the schema and re-indexing. Kishore Nallan clarified that enabling nested fields on an existing collection is not allowed. They suggested reproducing the issue with curl commands for a quicker solution.
Issues with Semantic Search in OpenAI Embeddings
Semyon was having issues while creating a schema for semantic search with OpenAI embeddings. Jason gave multiple suggestions for troubleshooting but none of them worked. The error was narrowed down to possibly being related to Semyon's specific OpenAI account or the OpenAI API key. The thread ended with Jason suggesting Semyon to check billing and make a direct API call to OpenAI.
1