medium severityWhyLabs data profile, whylogs logging
Profile views show NaN metrics for new/evolved columns, merge failures between profiles, or conflicting resolvers warnings when logging data with schema changes. In WhyLabs, incomplete profiles lead to inaccurate drift detection or data quality alerts.
Root cause
whylogs data profiles use schema-defined resolvers to compute metrics per column/data type; schema evolution (new columns, type changes) causes missing metrics (NaNs) or resolver conflicts when merging profiles with incompatible schemas, as profiles require matching column sets for merge operations.[whylogs Schema Configuration](https://whylogs.readthedocs.io/en/latest/examples/basic/Schema_Configuration.html)
whylogsWhyLabsdata profileschema evolutionmerge conflictNan metricsresolver conflict