Table of Contents

Search

  1. Preface
  2. Introduction to Hadoop Integration
  3. Before You Begin
  4. Amazon EMR Integration Tasks
  5. Azure HDInsight Integration Tasks
  6. Cloudera CDH Integration Tasks
  7. Hortonworks HDP Integration Tasks
  8. MapR Integration Tasks
  9. Appendix A: Connections

HBase Connection Properties for MapR-DB

HBase Connection Properties for MapR-DB

Use an HBase connection to connect to a MapR-DB table. The HBase connection is a NoSQL connection. You can create and manage an HBase connection in the Administrator tool or the Developer tool. HBase connection properties are case sensitive unless otherwise noted.
The following table describes the HBase connection properties for MapR-DB:
Property
Description
Name
Name of the connection. The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
ID
String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name.
Description
Description of the connection. The description cannot exceed 4,000 characters.
Location
Domain where you want to create the connection.
Type
Connection type. Select
HBase
.
Database Type
Type of database that you want to connect to.
Select
MapR-DB
to create a connection for a MapR-DB table.
Cluster Configuration
The name of the cluster configuration associated with the Hadoop environment.
MapR-DB Database Path
Database path that contains the MapR-DB table that you want to connect to. Enter a valid MapR cluster path.
When you create an HBase data object for MapR-DB, you can browse only tables that exist in the MapR-DB path that you specify in the
Database Path
field. You cannot access tables that are available in sub-directories in the specified path.
For example, if you specify the path as
/user/customers/
, you can access the tables in the
customers
directory. However, if the
customers
directory contains a sub-directory named
regions
, you cannot access the tables in the following directory:
/user/customers/regions

0 COMMENTS

We’d like to hear from you!