Thanks for such a nice explanation. I have one scenario, suppose if I create one mapping which uses incremental aggregation and run it, aggregations will be done and stored in files in the cache. Now if I need to create 2nd mapping which uses incremental aggregation, then where will the aggregations be stored?Will they be stored as new files in the same location or some other location?Each mapping aggregation files will be different from each other or they will use same files for storing aggregations for all the mappings
Hi Hemanth, Good Explanation. i have a doubt , you are updating the source database with the new column as Y. if the client wants that, there should not be any changes done on the source table(here emp) means what case we have to proceed with? i hope you are getting my scenario!!! If any one have idea about this scenario please post? Thanks in advance
Rakesh Raky Very good question.I am curious to know the answer.Your comment has already been 8 months, so let me know if you know the answer to your question.
Then may be we can implement this through lookup transformation. Means compare the source table's emp_id with the previous snapshot of the target table's emp_id.If the emp_id is already present in the target table then it is a old record else the emp_id is new one.Based on this comparison update the prev indicator field as 'N' and the update as 'Y' for the new one. Rest of the process will be same as shown in the video.
Great way of explanation brother. Understood well.
Really its very good. explain performance tunning concept with scenario
Perfect 👍 Thanks for the clean explanation
awesome explanation...never thought incremental aggregation can be explained so easily.
awesome again!! well done!
Hi, nice explanation.
Perfect video
Hi hemanth nice explanation...please continue with more scenario's
thank you for the video. Very good explanation.
very good explanation.. thank you :)
Hi Sir,
Very help in clear understanding. Thanks !@!!
Thanks for Good stuff ...
Hi sir ,
When we use incremental aggregate is it mandatory taking aggregate transformation in mapping level or no need . Plz tell me . Thanks
Thanks for such a nice explanation. I have one scenario, suppose if I create one mapping which uses incremental aggregation and run it, aggregations will be done and stored in files in the cache. Now if I need to create 2nd mapping which uses incremental aggregation, then where will the aggregations be stored?Will they be stored as new files in the same location or some other location?Each mapping aggregation files will be different from each other or they will use same files for storing aggregations for all the mappings
its very clear.. thanks
Good Explanation.
outstanding explanation
hi hamenth,
could you please explain more scenario's like this.......
thanks.
Hi Hemanth, Good Explanation. i have a doubt , you are updating the source database with the new column as Y. if the client wants that, there should not be any changes done on the source table(here emp) means what case we have to proceed with?
i hope you are getting my scenario!!!
If any one have idea about this scenario please post?
Thanks in advance
Rakesh Raky Very good question.I am curious to know the answer.Your comment has already been 8 months, so let me know if you know the answer to your question.
Then may be we can implement this through lookup transformation. Means compare the source table's emp_id with the previous snapshot of the target table's emp_id.If the emp_id is already present in the target table then it is a old record else the emp_id is new one.Based on this comparison update the prev indicator field as 'N' and the update as 'Y' for the new one. Rest of the process will be same as shown in the video.
Very clear explanation
Very nice explanation
Nice explaination
nice explanation
Hemanth nice Example
can u put the video about partitioning.
very clear explanation