snowplow / enrich

74%

master: 74%

LAST BUILD ON BRANCH switch_to_schema_violations

branch: switch_to_schema_violations

CHANGE BRANCH

x

Reset

• switch_to_schema_violations
• 3.8.x
• 4.1.0-cve-fix
• bug/api_enrichment
• bug/make-cookie-extractor-case-insensitive
• bump_libs
• cats_effect_3
• change-pii-example
• configurable_atomic_field_limits
• deprecate-stream-enrich
• develop
• enrich-nsq-default-region-chain
• feat/cross_navigation
• feature/azure-blob-storage-integration
• feature/azure_auth_methods
• feature/event-hub-oauth
• feature/gcp-attribution
• feature/license-config
• feature/multiple-azure-storage-account
• fix-docker-compose
• iglu-client-4.0.2
• incomplete_events
• incomplete_events_config
• incomplete_events_failure_data_fix
• incomplete_events_failure_entity
• incomplete_events_integration_test
• incomplete_events_metrics
• incomplete_events_unit_tests
• issue/815-mandrill_adapter_update
• issue/846-snowplow-limited-use-license
• issue/851-headset_platform
• js-headers
• js-params
• js-params-iife
• license-update
• mandrill-1-0-3
• master
• multiple-javascript-enrichments
• multiple-javascript-enrichments-tests
• observed_event
• print_event_stuck
• release/3.8.3
• release/3.9.0
• release/4.0.0
• release/4.0.1
• release/4.1.0
• release/4.2.1
• release_3.8.3
• replace-mysql-client
• schema-event-spec
• schema-violations-fix
• snapshot/switch_to_schema_violations
• stop-publish-jar
• test/cross-nav-it
• test/validate-enrich-4.0-cross-navigation
• too-long-atomic
• tracking_scenarios
• upgrade-kafka
• upgrade-kcl

Build # 8191412055

Build Type

Pull #883

github

Committed by benjben

Commit Message

Switch bad row type from EnrichmentFailures to SchemaViolations for some errors

There are 3 places that currently produce an EnrichmentFailures bad row
whereas the more appropriate type is SchemaViolations:

1. When the input fields of the HTTP requests are mapped to the atomic event.
2. When the enrichments contexts get validated.
3. When the atomic fields lengths get validated.

For 1 and 3, the error should be mapped into an Iglu ValidationError
with the atomic schema referenced.

Before this change, 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 unstruct event. Now all these errors are wrapped inside
a same SchemaViolations bad row.

Likewise, before this change when an enrichment context was invalid,
we were emitting a bad row right away and not checking the lengths of
the atomic fields. Now all these errors are wrapped inside a same
SchemaViolations bad row.

Pull Request Pull Request #883: Switch bad row type from EnrichmentFailures to SchemaViolations for s…

Run Details

108 of 124 new or added lines in 12 files covered. (87.1%)

28 existing lines in 7 files now uncovered.

4039 of 5425 relevant lines covered (74.45%)

1.19 hits per line