Solved

FeatureMerger or joiner - one to many

Forum|Forum|9 years ago
August 1, 2016
6 replies
1063 views

fmenewbie

HI, I want to join Table1 and Table2 and get Table3. should I use FeatureMerger or Joiner? both data sources are ESRI GDB tables.

Table 1

PropertyID100101

Table 2

TractIDPropertyID1000100100110110021001003102

Table 3

PropetyIDTractID100100010010021011001

Best answer by erik_jan

Both transformers could do this. The difference in this case could be in performance:

FeatureMerger needs all features to be read in the workspace. This option is better if most features are used in the join operation.

Joiner needs only one feature dataset in the workflow and will join to an external source. This option performs better if from the external source only a small part is joined. This way not the whole table has to be read.

Hope this helps supporting your choice.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

+23

erik_jan
Contributor
Best Answer
Forum|Forum|9 years ago
August 1, 2016

Both transformers could do this. The difference in this case could be in performance:

FeatureMerger needs all features to be read in the workspace. This option is better if most features are used in the join operation.

Joiner needs only one feature dataset in the workflow and will join to an external source. This option performs better if from the external source only a small part is joined. This way not the whole table has to be read.

Hope this helps supporting your choice.

Upvote

+18

itay
Supporter
Forum|Forum|9 years ago
August 2, 2016

Just dont forget to use the list setting for the 1:N relation

Upvote

+21

fmelizard
Safer
Forum|Forum|9 years ago
August 2, 2016

Both transformers could do this. The difference in this case could be in performance:

FeatureMerger needs all features to be read in the workspace. This option is better if most features are used in the join operation.

Joiner needs only one feature dataset in the workflow and will join to an external source. This option performs better if from the external source only a small part is joined. This way not the whole table has to be read.

Hope this helps supporting your choice.

Just did some looking and I believe the Joiner will be more efficient in this case because it stores the data it is joining to in a very compact efficient way. I'd start with Joiner anyway...