Currently the CheckAddDefinitionsFromAttributes utility in CollectionDefinition, when translating attributes into a workable definition, does not complain if both vector/ize attrs are provided with a (mismatched) Dimension each.
Same treatment for SimilarityMetric, which is also found on both (collection) attributes.
Very same situation for CreateTableDefinition in TableDefinition (minus the similarity metric bit)
This (post-GA) ticket is about throwing if this happens (to avoid silently swallowing user-provided inconsistencies).
Currently the
CheckAddDefinitionsFromAttributesutility in CollectionDefinition, when translating attributes into a workable definition, does not complain if both vector/ize attrs are provided with a (mismatched) Dimension each.Same treatment for SimilarityMetric, which is also found on both (collection) attributes.
Very same situation for
CreateTableDefinitionin TableDefinition (minus the similarity metric bit)This (post-GA) ticket is about throwing if this happens (to avoid silently swallowing user-provided inconsistencies).