How to use Pentaho MapReduce to convert raw weblog data into parsed, delimited records.
The steps in this guide include

1. Loading the sample data file into CLDB
2. Developing a PDI transformation which will serve as a Mapper
3. Developing a PDI job which will invoke a Pentaho MapReduce step that runs a map-only job, using the developed mapper transformation.
4. Executing and reviewing output

Prerequisites

In order to follow along with this how-to guide you will need the following:

• MapR
• Pentaho Data Integration
• Pentaho Hadoop Node Distribution

Sample Files

The sample data file needed for this guide is:

NOTE: If you have completed the Loading Data into the MapR filesystem guide, then the necessary file will already be in the proper location.
This file should be placed in CLDB at /weblogs/raw using the following commands.

hadoop fs -mkdir /weblogs
hadoop fs -mkdir /weblogs/raw
hadoop fs -put weblogs_rebuild.txt /weblogs/raw/

Step-By-Step Instructions

Setup

Start MapR if it is not already running.

Create a Mapper Transformation to Parse the Raw Weblog Data File

In this task you will create a mapper transformation that will parse the weblog file into an easier to use format.

1. Start PDI on your desktop. Once it is running choose 'File' -> 'New' -> 'Transformation' from the menu system or click on the 'New file' icon on the toolbar and choose the 'Transformation' option.
   
   
2. Add a Map/Reduce Input Step: You are going to read data as a mapper transformation, so expand the 'Big Data' section of the Design palette and drag a 'Map/Reduce Input' node onto the transformation canvas. Your transformation should look like:
   
   
   
   
3. Edit the Map/Reduce Input Step: Double-click on the 'Map/Reduce Input' node to edit its properties. Enter this information:
   1. Key Field Type: Enter String
   2. Value Field Type: Enter String
      When you are done your 'Map/Reduce Input' window should look like this:
      
      Click 'OK' to close the window.
      
      
4. Add a Regex Evaluation Step: You need to parse the record using a regular expression to get the information from the web log, so expand the 'Scripting' section of the Design palette and drag a 'Regex Evaluation' node onto the transformation canvas. Your transformation should look like:
   
   
   
   
5. Connect the Input and Regex Evaluation Steps: Hover the mouse over the 'Map/Reduce Input' node and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'Regex Evaluation' node. Your canvas should look like this:
   
   
   
   
6. Edit the Regex Evaluation Step: Double-click on the 'Regex Evaluation' node to edit its properties. Enter this information:
   1. Field to evaluate: Enter 'value'
   2. Result Fieldname: Enter 'is_match'
   3. Check 'Create fields for capture groups'
   4. Regular Expression: Enter

      ^([^\s]{7,15})\s            # client_ip
      -\s                         # unused IDENT field
      -\s                         # unused USER field
      \[((\d{2})/(\w{3})/(\d{4})  # request date dd/MMM/yyyy
      :(\d{2}):(\d{2}):(\d{2})\s([-+ ]\d{4}))\]
                                  # request time :HH:mm:ss -0800
      \s"(GET|POST)\s             # HTTP verb
      ([^\s]*)                     # HTTP URI
      \sHTTP/1\.[01]"\s           # HTTP version
      
      (\d{3})\s                   # HTTP status code
      (\d+)\s                     # bytes returned
      "([^"]+)"\s                 # referrer field
      
      "                           # User agent parsing, always quoted.
      "?                          # Sometimes if the user spoofs the user_agent, they incorrectly quote it.
      (                           # The UA string
        [^"]*?                    # Uninteresting bits
        (?:
          (?:
           rv:                    # Beginning of the gecko engine version token
           (?=[^;)]{3,15}[;)])    # ensure version string size
           (                      # Whole gecko version
             (\d{1,2})                   # version_component_major
             \.(\d{1,2}[^.;)]{0,8})      # version_component_minor
             (?:\.(\d{1,2}[^.;)]{0,8}))? # version_component_a
             (?:\.(\d{1,2}[^.;)]{0,8}))? # version_component_b
           )
           [^"]*                  # More uninteresting bits
          )
         |
          [^"]*                   # More uninteresting bits
        )
      )                           # End of UA string
      "?
      "

      
      
   5. Capture Group Fields: Add the following all with Type String
      1. client_ip
      2. full_request_date
      3. day
      4. month
      5. year
      6. hour
      7. minute
      8. second
      9. timezone
      10. http_verb
      11. uri
      12. http_status_code
      13. bytes_returned
      14. referrer
      15. user_agent
      16. firefox_gecko_version
      17. firefox_gecko_version_major
      18. firefox_gecko_version_minor
      19. firefox_gecko_version_a
      20. firefox_gecko_version_b
          
          When you are done your 'Regex Evaluation' window should look like this:
            
          
          
7. Permit whitespace and comments in regular expression: Switch to the 'Content' tab and check the 'Permit whitespace and comments in pattern' option. When you are done your window should look like:
   
   Click 'OK' to close the window.
   
   
8. Add a Filter Rows Step: You should always ensure you do not have any bad rows in your file that may break future processing, so expand the 'Flow' section of the Design palette and drag a 'Filter Rows' node onto the transformation canvas. Your transformation should look like:
   
   
   
9. Connect the Regex Evaluation and Filter Rows Steps: Hover the mouse over the 'Regex Evaluation' node and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'Filter Rows' node. Your canvas should look like this:
   
   
   
10. Edit the Filter Rows Step: Double-click on the 'Filter Rows' node to edit its properties. Enter this information:
    1. Click the <field> box to the left of the '=' box
    2. A 'Select a field:' window will appear. Select 'is_match' and click 'OK'.
       
    3. Click the <value> box
    4. A 'Enter value' box will appear. Enter 'Y' for Value and click 'OK'.
       
       When you are done your window should look like:
       
       Click 'OK' to close the window.
       
       
11. Add a Value Mapper Step: You may want to be able to use the month number instead of the 3 letter month, so expand the 'Transform' section of the Design palette and drag a 'Value Mapper' node onto the transformation canvas. Your transformation should look like:
    
    
    
12. Connect the Filter Rows and Value Mapper Steps: Hover the mouse over the 'Filter Rows' node and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'Value Mapper' node. When you release the mouse and a window appears select the 'Result is TRUE' option. Your canvas should look like this:
    
    
    
13. Edit the Value Mapper Step: Double-click on the 'Value Mapper' node to edit its properties. Enter this information:
    1. Fieldname to use: Select 'month'
    2. Target field name: Enter 'month_num'
    3. Default upon non-matching: Enter '0'
    4. Field Values: Enter the following:

       Source Value	Target Value
       Jan	1
       Feb	2
       Mar	3
       Apr	4
       May	5
       Jun	6
       Jul	7
       Aug	8
       Sep	9
       Oct	10
       Nov	11
       Dec	12

       
       When you are done your window should look like:
       
       Click 'OK' to close the window.
       
       
14. Add a Dummy Step: You always have to tell a Filter Rows node what to do with the rows that do not match, in this case we do not want to do anything with them, so expand the 'Flow' section of the Design palette and drag a 'Dummy (do nothing)' node onto the transformation canvas. Your transformation should look like:
    
    
    
15. Connect the Filter Rows and Dummy Steps: Hover the mouse over the 'Filter Rows' node and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'Dummy (do nothing)' node. When you release the mouse and a window appears. Select the 'Result is FALSE option. Your canvas should look like this:
    
    
    
16. Add a User Defined Java Expression Step: You need to concatenate your output fields together as a mapper transformation may only have two output fields a key and a value, so expand the 'Scripting' section of the Design palette and drag a 'User Defined Java Expression' node onto the transformation canvas. Your transformation should look like:
    
    
    
17. Connect the Value Mapper and Java Expression Steps: Hover the mouse over the 'Value Mapper' node and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'User Defined Java Expression' node. Your canvas should look like this:
    
    
    
18. Edit the User Defined Java Expression Step: Double-click on the 'User Defined Java Expression' node to edit its properties. Enter this information:
    1. New field: Enter 'output_value'
    2. Java Expression: Enter

       client_ip + '\t' + full_request_date + '\t' + day + '\t' + month + '\t' + month_num + '\t' + year +
       '\t' + hour + '\t' + minute + '\t' + second + '\t' + timezone + '\t' + http_verb + '\t' + uri + '\t' +
       http_status_code + '\t' + bytes_returned + '\t' + referrer + '\t' + user_agent

    3. Value Type: Select 'String'
       When you are done your window should look like:
       
       Click 'OK' to close the window.
       
       
19. Add a Map/Reduce Output Step: You need to output your results to the Map/Reduce framework, so expand the 'Big Data' section of the Design palette and drag a 'Map/Reduce Output' node onto the transformation canvas. Your transformation should look like:
    
    
    
20. Connect the Java Expression and Output Steps: Hover the mouse over the 'User Defined Java Expression' node and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'Map/Reduce Output' node. Your canvas should look like this:
    
    
    
21. Edit the Output Step: Double-click on the 'Map/Reduce Output' node to edit its properties. Enter this information:
    1. Key field: Select 'key'
    2. Value field: select 'output_value'
       When you are done your window should look like:
       
       Click 'OK' to close the window.
       
       
22. Save the Transformation: Choose 'File' -> 'Save as...' from the menu system. Save the transformation as 'weblog_parse_mapper.ktr' into a folder of your choice.

Create a PDI Job to Execute a Map Only MapReduce Process

In this task you will create a job that will execute a "map-only" MapReduce process using the mapper transformation you created in the previous section.

1. Within PDI, choose 'File' -> 'New' -> 'Job' from the menu system or click on the 'New file' icon on the toolbar and choose the 'Job' option.
   
   
2. Add a Start Job Entry: You need to tell PDI where to start the job, so expand the 'General' section of the Design palette and drag a 'Start' node onto the job canvas. Your canvas should look like:
   
   
   
3. Add a Pentaho MapReduce Job Entry: Expand the 'Big Data' section of the Design palette and drag a 'Pentaho MapReduce' job entry onto the job canvas. Your canvas should look like:
   
   
   
4. Connect the Start and MapReduce Job Entries: Hover the mouse over the 'Delete folders' job entry and a tooltip will appear. Click on the output connector (the green arrow pointing to the right) and drag a connector arrow to the 'Pentaho MapReduce' job entry.
   Your canvas should look like this:
   
   
   
5. Edit the MapReduce Job Entry: Double-click on the 'Pentaho MapReduce' job entry to edit its properties. Enter this information:
   1. Hadoop Job Name: Enter 'Web Log Parser'
   2. Mapper Transformation: Enter <PATH>/weblog _parse_mapper.ktr
      <PATH> is the folder path you saved the mapper in.
   3. Mapper Input Step Name: Enter 'Map/Reduce Input'
   4. Mapper Output Step Name: Enter 'Map/Reduce Output'
      When you are done the window should look like:
      
      
      
6. Configure the MapReduce Job: Switch to the 'Job Setup' tab. Enter this information:
   1. Check 'Suppress Output of Map Key'
   2. Input Path: Enter '/weblogs/raw'
   3. Output Path: Enter '/weblogs/parse'
   4. Input Format: Enter 'org.apache.hadoop.mapred.TextInputFormat'
   5. Output Format: Enter 'org.apache.hadoop.mapred.TextOutputFormat'
   6. Check 'Clean output path before execution'
      When you are done your window should look like:
      
      
      
7. Configure the Cluster Properties: Switch to the 'Cluster' tab. Enter this information:
   1. Hadoop distribution: Select 'MapR'
   2. Working Directory: Enter '/tmp'
   3. HDFS Hostname, HDFS Port, Job Tracker Hostname, Job Tracker Port: Your connection information. For a local single node cluster leave blank.
   4. Number of Mapper Tasks: Enter '3'. You can play around with this to get the best performance based on the size of your data and the number of nodes in your cluster.
   5. Number of Reducer Tasks: Enter '0'
   6. Check 'Enable Blocking'
   7. Logging Interval: Enter '10'. The number of seconds between pinging MapR for completion status messages
      When you are done your window should look like:
      
      Click 'OK' to close the window.
      
      
8. Save the Job: Choose 'File' -> 'Save as...' from the menu system. Save the transformation as 'weblogs_parse_mr.kjb' into a folder of your choice.
   
   
9. Run the Job: Choose 'Action' -> 'Run' from the menu system or click on the green run button on the job toolbar. An 'Execute a job' window will open. Click on the 'Launch' button. An 'Execution Results' panel will open at the bottom of the PDI window and it will show you the progress of the job as it runs. After a few seconds the job should finish successfully:
   

If any errors occurred the job entry that failed will be highlighted in red and you can use the 'Logging' tab to view error messages.

Check MapR for Parsed Weblog Data

1. If you have mounted your MapR CLDB onto your local machine you may verify the file loaded by navigating to the MapR directory.

   ls /mapr/my.cluster.com/weblogs/parse

   This should return:
   _logs part-00000 part-00001 part-00002 _SUCCESS
   
2. If you have not mounted your MapR CLDB onto your local machine you may alternatively check MapR by:

   hadoop fs \-ls /weblogs/parse

   
   This should return:
   -rwxrwxrwx 3 demo demo 27132365 2012-01-04 16:52 /weblogs/parse/part-00001
   -rwxrwxrwx 3 demo demo 0 2012-01-04 16:52 /weblogs/parse/_SUCCESS
   -rwxrwxrwx 3 demo demo 27188268 2012-01-04 16:52 /weblogs/parse/part-00002
   drwxrwxrwx - demo demo 1 2012-01-04 16:52 /weblogs/parse/_logs
   -rwxrwxrwx 3 demo demo 27147417 2012-01-04 16:52 /weblogs/parse/part-00000

Summary

During this guide you learned how to create and execute a Pentaho MapReduce job to parse raw weblog data.