Skip to main content

$LOOKUP ( Similar to LEFT OUTER JOIN in RDBMS) in MongoDB

In RDBMS, we have different type of joins to join the tables and get the required data from joined tables. As MongoDB is a NO Sql database, MongoDB will not support those type of joins. But we can implement LEFT OUTER JOIN using $lookup function in MongoDB. This function is there in MongoDB 3.2 version. To join two collections we need to have a common field in both the collections. $lookup works with aggregate function only.

Syntax:
db.collection1.aggregate([
 {
    $lookup:
      {
         from:"collection2",
         localField:"common field name from collection1",
         foreignField:"common field name from collection2",
         as:"Alias name for collection2"
     }
 }
])


Here in above syntax,
collection1 -- Collection name which is acts like parent table.
collection2 -- Collection name which is acts like child table and this will be joined with collection1.
"common field name from collection1" -- Join column from collection1.
"common field name from collection2" -- Join column from collection2.
"Alias name for collection2" -- Alias name for collection in output and this acts as an array in result.

 Consider the below example:

Collection1 (named department):



Collection2 (named employee):




In first collection "department", we have "dept No" and In second collection employee, we have "Dept No". Now, am joining these two collections using common field "Dept No".


I want to map all the employee details to corresponding department numbers in the result set. To do this, I need to pass the below command.

db.department.aggregate([
{
  $lookup:
   {
      from:"employee",
      localField:"dept No",
      foreignField:"Dept No",
      as:"Emp_Details"
   }
 }
])

Output of the above command:


 If we want filter the records before join, then we need to use $match function. Let's assume that, we want to get the department records and corresponding employee details where department number is 101. To do this, we need to use below command.


db.department.aggregate([
 {
    $match:
     {
        "dept No":101
     }
 },
{
  $lookup:
   {
      from:"employee",
      localField:"dept No",
      foreignField:"Dept No",
      as:"Emp_Details"
   }
 }
])

Result set of the above command:





If You want to restrict the number of fields to be displayed in result set, you can use $project function along with the $lookup and $match.

In the below query, I am restricting the number of fields to 4(department number and name,employee name and seat number).

db.department.aggregate([
{
    $match:{"dept No":101}
},
{
    $lookup:
        {
            from:"employee",
            localField:"dept No",
            foreignField:"Dept No",
            as:"Emp_Details"
        }
},
{
    $project:
        {
            "Dept Name":1,
            "dept No":1,
            "Emp_Details":{"Emp Name":1,"Emp Seat No":1}
        }
}
])

Hope, This has given you a brief idea about join in MongoDB.

Comments

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',...

Updating Target Table in Informatica

Generally, in every project we will see at least one requirement to update target based on some conditions. Case1: When we have primary key defined on table in Database Case2:   When we do not have primary key defined on table in Database Case3: When we want to update target based on non-primary key field. Let’s discuss it in detail. Case1: When we have primary key defined on table in Database After creating table in DB, import table as target along with primary key constraints. After done with importing, we can check the primary key details by editing target in target definition. In this case, we can use update strategy to update target table. Suppose, we have a table called RETURN_CD and primary key ROW_WID defined on that table. Now, we can update target table using update strategy based on primary key. In mapping, we should connect primary key port and the ports which we want to update in target table. Please check the below screenshot. And ...