Hi
In the join transformation, could we have a 'natural mode' switch to make join on all the common fields between the 2 tables.
Regards
Hi
In the join transformation, could we have a 'natural mode' switch to make join on all the common fields between the 2 tables.
Regards
Hi
I have to migrate a kimball style datawarehouse to a datalake so I need to generate flat files from star/snowflake schema
i.e.:
sales fact ā product ā product sub category ā product category
sales fact ā geography ā sales territory
sales fact ā promotion
I would like to create a loop that browse up the foreign keys and create a flat file containing the facts and all the dimension attributes
I canāt do it because I need to define case by case the matching columns in the EM Join table transformation.
A natural join transformation would make the join on all the matching column names and inject all the non matching columns.
It would reproduce the behavior of the Join instruction of Qlik.
Used in an iterate loop, I could have an automated process to migrate datawarehouses to data catalog and be sure I donāt miss a column
Regards
Hello Christophe,
Iām not sure if it can help, and others might have better ideas, but my initial try on this would be as follows:
I have sketched it out in a small .morph project (simplified into a single module), but in doing this I realize:
KR
David
idea_for_Natural join switch option.morph (14.4 KB)
Note that, given this is a feature request, the addition of a ānatural joinā option would indeed be great (to avoid the logic I describe above).
In this same regard, it would be great if the Merge action was expanded by:
Sincere apologies for hijacking this post, just sharing some thoughts!
David,
Thanks for post, itās always valuable to go deep in this kind of thoughts.
Indeed, Iām just looking for a simple way to reproduce the Qlik join instruction.
So it would be based on equal field names.
Iāve built a workaround by generating SQL scripts with EM but this is quite cumbersome.
Iād like it to be a specific transformation and not some options to activate in the existing Join transformation.
Regards
Interesting! Never thought of such a use case. Effectively, itās about being able to dynamically define fields to join.
The capabilities to work in ādynamicā mode with EM are very powerful but 3 transformations canāt be used (as far as I can see) : the Join, the Unpivot and the keep/remove matching. for the Unpivot I would need a switch between āpivot columns exceptā (as it is now) and āpivot only these columnsā. For the keep/remove, I often use it before a Join to make it an āinnerā join.
Dynamic mode is rarely possible on ETL tools as they are column based (you design the transformation flow by column). EM is table based, you can create transformation without knowing in advance the table profil.
Maybe you have here a good subject for a linkedin post ?
Regards
UPDATE
The āNatural mergeā action is confirmed for v5.6 and is planned for release in a couple of weeks. It will have 4 modes:
Hi,
Thanks, it's very powerful and time saving. I love it.
Regards