I don’t know if this is a bug in build 25220, or if it’s the intended behavior. But it’s very different from past versions, and will likely cause issues in our workflows.
When the ‘Merge Attributes’ option is unchecked, no Candidate attributes are carried forward in the Passed port as a shown in this screenshot. The Candidate attributes are only carried forward in the Failed port.
If the ‘Merge Attributes’ is checked, the attributes are passed:
However, the issue is that there is no configuration in the ‘Merge Attributes’ section that will only pass the original attributes from the Candidate. You are forced to either merge the Filter attributes, create a prefix on the Filter attributes (and likely have to remove in bulk post-SpatialFilter), or simply use the Filter attributes. No option will spatially filter the Candidates without altering the schema.
I’ve found this behavior in many transformers that have the ‘Merge Attributes’ option, including SpatialFilter, SpatialRelator, PointOnAreaOverlayer, PointOnLineOverlayer, and LineOnAreaOverlayer.
EDIT: After this was posted, I’m now seeing others that have already pointed this out. Can we get an update on if this has been addressed in all transformers in a build after 25220?
