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

Looping using Expression Transformation in Informatica

One of the most common used transformation in Informatica is Expression transformation. In Expression transformation we can perform various operations such as data conversions i.e to_date,to_char, string manipulation such as substr,instr etc. Now coming to one of the widely and prominent task which we perform using Expression transformation is looping a value. Expression transformation has three types of ports i.e. input,variable and output.Only output port values can be propagated to next transformations. So in order to pass values of input and variable ports to next level of transformation these must be assigned to output ports.The order of execution in Expression transformation is top to bottom and first input then variable and finally output ports are processed. let us consider the following scenario   The files should be generated with employee name as file name and that particular file should have the details of that respective employee only, if the employee has more than

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.

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',