Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.
Number of Attributes After Join Operation
suleymansahal
Member Posts: 27 
Contributor II
Hi everyone,
After joining two datasets the Join Operator removes double attributes. However, I am seeing the removed attributes on the metadata popup window when I hover on the output node. I also see removed attributes in the list of Select Attributes Operator. Is this a bug or an intended result? I wonder If somebody could explain.
After joining two datasets the Join Operator removes double attributes. However, I am seeing the removed attributes on the metadata popup window when I hover on the output node. I also see removed attributes in the list of Select Attributes Operator. Is this a bug or an intended result? I wonder If somebody could explain.
Tagged:
0
Answers
Hello
Take a look at these links please:
https://rapidminer.com/blog/tips-tricks-different-ways-to-join-data/#:~:text=Inner%20or%20Outer%2C%20Right%20or,match%20the%20records%20up%20with.
https://docs.rapidminer.com/latest/studio/operators/blending/table/joins/join.html
I hope this helps
Sara
maybe your definition of double attributes differs from RapidMiner's.
One instance of the duplicate attribute names is being kept by the Join operator. This is absolutely intentional. (In cases when the same attribute name has different contents in the example sets, you also want to keep the duplicate attributes.)
Also, the duplicate check is very thorough. Attribute names "data" and "Data" are already different enough to keep.
Regards,
Balázs