Skip to main content

Error message

When this error occurs

Each field or nested node is either primitive or non-primitive, and the configuration fields must match: This error is raised when both sets of fields appear on the same node. The design is intentional: primitive and non-primitive nodes have fundamentally different stat semantics, and mixing them creates ambiguous configurations.

Example: request that triggers this error

The address field has both enabled_stats (primitive) and properties (non-primitive).

How to fix

Choose the appropriate config shape for the field’s actual schema type: If the field is an object (non-primitive):
Use self for stats on the container column and properties for named children. If the field is a primitive (string, integer, etc.):
Remove properties, items, and self.