You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Impression-stats and other docTypes have a release top-level field that should be used in the pipeline as input to normalized_channel. Currently, they have null normalized_channel.
The text was updated successfully, but these errors were encountered:
We should probably encode this in JSON schemas under mozPipelineMetadata as a new normalized_channel_source field and have the pipeline use that to decide where to look.
That would make this more generally applicable compared to supporting just normalized_channel. We'd have to think carefully about the interface and what to call the fields.
Thinking more about interface, this could be cast as attribute_mappings similar to the existing jwe_mappings. Each mapping would have a required attribute field and then either a static_value or source_path field.
For a value like normalized_channel, though, this isn't quite powerful enough. The source_path would generally be pointing to a "raw" channel identifier; the value still needs to go through the NormalizeAttributes#channel logic. So I suppose we'd be populating attribute app_update_channel via this metadata, and we still rely on the pipeline knowing about this as the attribute to use as source for normalization.
Impression-stats and other docTypes have a
release
top-level field that should be used in the pipeline as input to normalized_channel. Currently, they have null normalized_channel.The text was updated successfully, but these errors were encountered: