Min Partition Size Anomaly Reporting
How the Min Partition Size check reports violations: the Shape Anomaly it produces, what the numbers mean, and how a partition-level anomaly differs from a row-level one.
Anomaly Messages
Min Partition Size always reports a Shape Anomaly, one per failing partition. There is no Record Anomaly: the rule evaluates a count, not individual rows, so there is no offending row to point at.
Shape Anomaly
Reading the message:
<value>is the Minimum partition size configured on the check.<record_count>is the number of records actually loaded from that partition.<partition>is the name of the partition that failed, which is the file name for a file container and the loaded slice for a table.
Because the anomaly is raised against the partition rather than against a set of rows, the Source Records view does not list violating records: there are none to list. What the anomaly gives you is the partition name and the two counts.
Custom Anomaly Description does not apply to this rule. The option replaces the message on Record Anomalies, and Min Partition Size emits a Shape Anomaly only.
See Also
-
Examples
Three production scenarios with the resulting anomaly message and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for choosing a threshold, sizing it against real loads, and pairing the rule with its counterpart.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
How It Works
The complete reference: definition, what a partition is, the minimum partition size property, and why the rule takes no field, filter, or coverage.