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

Types of Joins in Oracle/Teradata

In Data warehousing, irrespective of schema (snow flake schema or star schema) we are using, we should join dimension and fact tables to analyze the business. Below are the frequently used joins: Inner join Left outer Join Right outer Join Cross join Inner Join: Inner join will give you the matching rows from both the tables. If the join condition is not matching then zero records will return. We should use ON keyword to give join condition. Example: Table1: ID Name 1 Krishna 2 Anirudh 4 Ashok Table2: ID Location 1 Bangalore 3 Chennai 4 Chennai We can join above two tables using inner join based on key column ID. SELECT T1.ID, T1.Name, T2.Location FROM Table1 T1 INNER JOIN Table2 T2 ON T1.ID = T2.ID     If we are using inner join, it will give us matching rows from both the table. Here in this example, we have 2 matching rows i.e. ID 1 and 4. Below will be the result set for the above exa...

Target Load Type - Normal or Bulk in Session Properties

We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.