***Note from Migration:***
Original Title was: Change Feature Joiner behavior so records with Null in the left join on field are not ignored
Currently, if you use Feature Joiner to join two data sets and you set it to be a Left join the Left join On field is null, the record will NOT emerge from the joined port. This is contrary to what one would expect from a left hand join where ALL records from the left table should emerge from the port (eg as in ESRI, MS Access, SQL etc). This is dangerous behavior and will no doubt cause a huge number of errors.
To get something that looks like an actual left join, you have to filter out the null values in the left key and add them back in later, which is utterly crazy in my opinion.
Please could you either change the behavior so that a left join behaves as would be expected, change the nomenclature so that you don't use left, right join etc (the very nature of naming conventions the transformer makes it seem more SQL like) or at the very least have a warning to indicate it is unable to process null keys.
