class Orchestrate::API::IndexingConflict
When a new collection is created by its first KV document, a schema is created for indexing, including the types of the values for the KV document. This error will occur when a new document provides values with different types. Values with unexpected types will not be indexed. Since search is an implicit feature of the service, this is an error and worth raising an exception over.
@example This is the example provided to me by the Orchestrate
team:
client.put(:test, :first, { "count" => 0 }) # establishes 'count' as a Long client.put(:test, :second, { "count" => "none" }) # 'count' is not a Long