FME join transformers always reject features with null or missing attribute values.

FME join transformers always reject features with null or missing attribute values.

• A. True
• B. False
• C. Sometimes
• D. Always

Answer: (B)

Join operations in FME hinge on join keys. A null or missing value on a join key cannot form a match, so in a strict inner join such features won’t obtain joined attributes and may be dropped. But you can configure the Joiner to keep unmatched features (left, right, or full outer join behavior) or to pass through features that don’t find a match, resulting in output where the joined attributes are empty for those features. Because of these options, features with null or missing join values are not always rejected—they can be preserved depending on the join type and settings.

Join operations in FME hinge on join keys. A null or missing value on a join key cannot form a match, so in a strict inner join such features won’t obtain joined attributes and may be dropped. But you can configure the Joiner to keep unmatched features (left, right, or full outer join behavior) or to pass through features that don’t find a match, resulting in output where the joined attributes are empty for those features. Because of these options, features with null or missing join values are not always rejected—they can be preserved depending on the join type and settings.