The latest articles on DEV Community by Sudarshan Sreenivasan (@sudarshan89). https://dev.to/sudarshan89 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1071154%2F6b5cdbd3-9dd6-4742-9ec8-0dd9e26dc768.png https://dev.to/sudarshan89 en Sudarshan Sreenivasan Sun, 12 Apr 2026 08:13:53 +0000 https://dev.to/sudarshan89/intentional-decomposition-5gf5 https://dev.to/sudarshan89/intentional-decomposition-5gf5 <p>I find it easy to understand certain concepts with help of diagrams and this is certainly one of them.</p> <p>Lets assume that our secondary sorting is on a composite key made out of Last Name and First Name.</p> <p>Composite Key</p> <p>With the composite key out of the way, now lets look at the secondary sorting mechanism</p> <p>Secondary Sorting Steps</p> <p>The partitioner and the group comparator use only natural key, the partitioner uses it to channel all records with the same natural key to a single reducer. This partitioning happens in the Map Phase, data from various Map tasks are received by reducers where they are grouped and then sent to the reduce method. This grouping is where the group comparator comes into picture, if we would not have specified a custom group comparator then Hadoop would have used the default implementation which would have considered the entire composite key, which would have lead to incorrect results.</p> <p>Overview of MR steps</p> analytics discuss management watercooler