4.2.0
This release brings a few changes in some bad rows emitted by Enrich.
What's new
Switch from EnrichmentFailures to SchemaViolations for some errors
The following errors were previously emitted as EnrichmentFailures bad rows and will now get emitted as SchemaViolations (against atomic schema):
- When the context added by an enrichment is invalid.
- When something goes wrong when the input fields of the HTTP request are mapped to the fields of the enriched event (e.g. when
tr_ttis converted from string to number and mapped totr_total). - When an atomic field is longer than the limit.
More errors wrapped inside a same bad row
Before 4.2.0, if there was any error in the mapping of the atomic fields, a bad row would get emitted right away and we would not try to validate the entities and unstructured event. All these errors are now wrapped inside a same SchemaViolations bad row.
Likewise, before 4.2.0, when an enrichment context was invalid, we were emitting a bad row right away and we were not checking the lengths of the atomic fields. Now all these errors are wrapped inside a same SchemaViolations bad row.
So 4.2.0 is more exhaustive in the errors that get wrapped inside a bad row.
Upgrading to 4.2.0
When upgrading from 4.0.0 or 4.1.0, there is only need to bump the version.
Check out Enrich documentation for the full guide on running and configuring the app.