Skip to main content
Solved

FeatureMerger or joiner - one to many


Forum|alt.badge.img

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.

View original
Did this help you find an answer to your question?

6 replies

erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • Best Answer
  • 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.


itay
Supporter
Forum|alt.badge.img+16
  • Supporter
  • August 2, 2016

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


fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • August 2, 2016
erik_jan wrote:

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...


Forum|alt.badge.img
  • Author
  • August 2, 2016
itay wrote:

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

Can you please tell me where to check the 1:N relation in FeatureMerger? Appreciate it!


erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • August 2, 2016
fmenewbie wrote:

Can you please tell me where to check the 1:N relation in FeatureMerger? Appreciate it!

In the setting to use duplicate suppliers. Then provide a list to store the duplicate suppliers.


Forum|alt.badge.img
  • Author
  • August 2, 2016
itay wrote:

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

@erik_jan. ok, I have set Process Duplicate Suppliers to Yes. Should I use Merged or DuplicateSupplier port for output?


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings