Maybe I'm not understanding control containers properly. Since there is no data being passed in the false branch (i.e all ages are at least 30), the field "info2" shouldn't have even been added to the union tool? I don't want metadata from both branches being unioned, only the stream that had data, which will always be one or the other.
When the metadata from both get added, it causes a downstream conflict.
My ultimate goal is for a simple way to only have one stream of data be passed based on my condition. Please let me know what I'm doing wrong.
@fiddycodes Rename Info2 column as Info.
I can't due that because these are two different fields.
I don't use these tools ---> but this sounds like a bug. in a standard container set up (disable/enable) with a macro or app you would not see this issue. expectation should be that if the control containers are configured correctly and only one flows to the union -> only one data source/schema flows through.
architecturally --- I'm not sure if this is the best design but my critique's of the workflow design aren't what's relevant here - it looks like a bug.