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
For RUN_MODEL jobs the key should be the model output key while for RUN_FLOW jobs the key should be the name of the flow output node. These should be controlled attrrs (i.e. .named trac_*). We need to decide whether to use the same attr for model and flow outputs, or whether to use different ones.
Description of Problem:
Currently there is no standard controlled tag attr added to job outputs by TRAC. Attrs can be added by configuring a flow/job to add them, but we want a standard contrtolled tag that is always supplied by TRAC and cannot be editted by users, as part of the audit history of where a dataset came from.
Potential Solutions:
See above.
The text was updated successfully, but these errors were encountered:
This is already done, trac_job_output is added to every output created by a job. For RunModelJob the output key is the model output key, for RunFlowJob the output key is the flow output node name.
Feature Request
For RUN_MODEL jobs the key should be the model output key while for RUN_FLOW jobs the key should be the name of the flow output node. These should be controlled attrrs (i.e. .named trac_*). We need to decide whether to use the same attr for model and flow outputs, or whether to use different ones.
Description of Problem:
Currently there is no standard controlled tag attr added to job outputs by TRAC. Attrs can be added by configuring a flow/job to add them, but we want a standard contrtolled tag that is always supplied by TRAC and cannot be editted by users, as part of the audit history of where a dataset came from.
Potential Solutions:
See above.
The text was updated successfully, but these errors were encountered: