Ecommerce Search Engine with User-added Products
TLDR Max seeks advice on handling a boolean field showing if a product is already in a user's cart for an ecommerce search engine. Kishore Nallan suggests waiting for the future "join" feature to allow merging separate indexes at query time.
Mar 31, 2023 (8 months ago)
I would then, somehow (😇), do a multi index query or multi query to check if, for the current user, the products in his search results have already been added to shopping cart by adding a boolean. Is this possible ?
Kishore Nallan10:03 AM
Good new: we're acutely aware of this need and have kicked off work to implement this feature. However, it's going to take some time before I can share a build for you to test it, given the scope and depth of the changes involved.
Kishore Nallan10:04 AM
With a multi search query I can have the ecommerce products and a list of products already added for a specific user. I will be able to add a display to a product if this product within the query results has already been added. But do you confirm that I cannot exclude products already added (query1) from global product results (query 2) ?
Kishore Nallan10:12 AM
Once the JOIN feature is live on the engine, we will be able to do it with only one query ? My use case here is like a SQL LEFT OUTER JOIN
Kishore Nallan10:17 AM
Screen 1 is a product document from product index
Screen 2 is a user document from user_feature index
With this structure, will I be able to exclude all product ids (added_products in user document) from query results in the product index ? All the added product ids from a user document IS EQUAL to a product index document id
Kishore Nallan10:42 AM
Indexed 3011 threads (79% resolved)
User-Specific Tagging and Filtering in UI
bnfd asked for the best way to create user-specific tags available on the UI. Jason suggested using personalized filters and creating a separate collection for each user's movies. The duo clarified the use of 'tags' in schemas and the refinementList widget in instantsearch. They also discussed various approaches to import and search large document collections.
Including All Individual Documents in a Group in Typesense
Magnus was uncertain how to include all documents within a group in Typesense, and specifically asked about ecommerce product cards. Jason published a new version of Typesense Instantsearch Adapter and advised storing all variant information for a product on each document. Magnus confirmed this as a viable solution.
Discussions on Typesense, Collections, and Dynamic Fields
Tugay shares plans to use Typesense for their SaaS platform and asks about collection sizes and sharding. Jason clarifies Typesense's capabilities and shares a beta feature. They discuss using unique collections per customer and new improvements. Kishore Nallan and Gabe comment on threading and data protection respectively.
Implementation and Optimization of 'Similar Products' Feature
Stefan is considering using "curation" for pre-calculating similar products. Kishore Nallan suggests using preset API, but Stefan raised an issue with sorting based on non-stored values. The issue remains open for resolution.
Discussing Document Indexing Speeds and Typesense Features
Thomas asks about the speed of indexing and associated factors. The conversation reveals that larger batch sizes and NVMe disk usage can improve speed, but the index size is limited by RAM. Jason shares plans on supporting nested fields, and they explore a solution for products in multiple categories and catalogs.