Skip to content

Modularise in-file metadata configuration

Maciej Pawel Szymanski requested to merge maszyman/athena:23.0-maszyman-modular-md-setup into 23.0

This MR builds on !61368 (merged) to modularise the in-file metadata configuration. It requires each workflow to explicitly specify which metadata category should be configured created and added to the output stream (nothing added created by default). By default, all the metadata found in the input will be propagated using the relevant tools (can be turned off with propagateMetadataFromInput=False).

I decided to keep a single function (although a bit renamed wrt !61368 (merged)) for propagation and one for creation for each category with an extra argument instead of splitting it into dedicated bits, but I'm open to suggestions. To keep some compatibility with event data configuration, the requested for creation metadata categories are passed as a list of strings, e.g. ["ByteStreamMetaData"]

Note that I not yet incorporated !61962 (merged) (probably better to wait for merging). [Edit: Done]

Edited by Maciej Pawel Szymanski

Merge request reports