#community-help

Issue with Object Field Validation in Emplace Mode

TLDR Elian identified a problem with object field validation in emplace mode. Jason provided a patch in the new build, which Elian confirmed resolved the issue.

1mo

Join the chat

Aug 06, 2023 (1 month ago)

Photo of md5-5de689a503621ea187403913ec03d9eb

Elian

12:21 PM

I think there is an issue with validation of object fields in the emplace mode:
• I defined an object "price" and fields below that, e.g. "price.default.ch.price". Those are optional:false
• If I create a document or import them via create, it fails with an error if a required field fails
• If I import the documents with mode emplace, it returns an error, but still imports it which invalidates the data in the schema
• Follow-up actions on the schema such as adding a field are not possible anymore
Attached a shell script to reproduce it - let me know if I missed anything

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

02:08 PM

Thanks for the detailed steps. I'm able to reproduce the issue. I will get back to you after investigating into why this is happening.

Aug 08, 2023 (1 month ago)

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

06:34 PM

Elian We’ve pushed out a new build with a patch for this issue. If you go to Cluster Configuration > Modify you should now see 0.25.0.rc62. Could you upgrade to it and let me know if you still see this issue?

06:34

Jason

06:34 PM

Thank you for again for the detailed steps with curl! That’s usually half the battle! 🙂

Elian

06:35 PM

It actually helped me to nail it down - I initially suspected that it's a general issue with the import and was surprised it worked - until I figured out that the difference was the action 🙂

06:43

Elian

06:43 PM

✅ Same behaviour now with emplace, thanks!

Jason

06:46 PM

Awesome, thank you for confirming!

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Handling Kinesis Stream Event Batching with Typesense

Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.

20mo

Resolving Error with Incorrect Field Type during Schema Update

Samuel encountered an error updating the schema for an existing collection. Kishore Nallan suggested specifying a concrete type, and later found inconsistent data within the collection that caused the error.

6mo

Issue with Field Indexing and Multiple Data Types

Raymond encountered an issue where a field seemed to be indexed twice and hence couldn't be deleted. Jason advised upgrading to a patch version, but the problem remained. Kishore Nallan suspected a race condition and an issue with conflicting data types. An effective solution wasn't achieved.

13mo