Table of Contents

Search

  1. Preface
  2. Installing Informatica MDM - Relate 360
  3. Configuring Relate 360
  4. Configuring Security
  5. Setting Up the Environment to Process Streaming Data
  6. Configuring Distributed Search
  7. Packaging and Deploying the RESTful Web Services
  8. Troubleshooting

Installation and Configuration Guide

Installation and Configuration Guide

Adding the Distributed Search-Related Parameters to the Configuration File

Adding the Distributed Search-Related Parameters to the Configuration File

Before you generate the coprocessor JAR file, you must update the configuration file to include the parameters related to distributed search.
  1. Open the configuration file in a text editor.
  2. Add the following parameters within the
    HBASEConfiguration
    section:
    CoprocessorPath
    Absolute path and file name for the coprocessor JAR file that you must generate and deploy in HDFS. The JAR file contains the search logic that the region servers use to perform searches.
    For example,
    /user/cloudera/db-hbase-coprocessorDeploy.jar
    .
    Use the following name format for the JAR file name:
    db-hbase-coprocessor<id>
    The name format uses the
    id
    parameter that indicates a unique identifier for the JAR file. For example, if
    id=Deploy
    , the JAR file name must be
    db-hbase-coprocessorDeploy.jar
    .
    CoprocessorClass
    Name of the class that the coprocessor uses. Specify
    com.informatica.mdmbde.database.hbase.coprocessor.BDRMRegionObserver
    as the parameter value.
    ScanCacheSize
    Optional. Number of records to pass to scanners at once. Adjust the value of the
    ScanCacheSize
    parameter based on the
    ScanMaxResultSize
    parameter.
    A lower value can result in multiple scans that might affect the performance of the jobs. A higher value can result in the failure of jobs if the size of the records exceeds the value of the
    ScanMaxResultSize
    parameter.
    Default is 500.
    ScanMaxResultSize
    Optional. Maximum size of records in bytes to return to scanners at once. Adjust the value of the
    ScanMaxResultSize
    parameter based on the
    ScanCacheSize
    parameter.
    A lower value can result in multiple scans and a higher value can result in increased memory usage that might affect the performance of the jobs.
    Default is 2097152.


Updated June 27, 2019