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
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):self for stats on the container column and properties for named children.
If the field is a primitive (string, integer, etc.):
properties, items, and self.
Related errors
- EmptyNodeConfig — node with no configuration at all
- UnsupportedSelfStats — only
null_value_countallowed inself

