Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

About Connect HBase rules

Updated on August 10, 2022

Connect HBase rules support interactions between Pega Platform and Apache HBase data stores by performing reading and writing operations on a single row identified by the unique row ID.

The following tabs are available on this form:

  • Service
  • Mappings
Note: There is a new form of the HBase rule. While you cannot create any new instances of the Pega 7.1.7 HBase rule, legacy instances in your application remain functional. For details see the Service tab.


To list the Connect HBase rules in your application, use the Application Explorer or click ConfigureIntegrationConnector Definitions & Simulations.

To list all Connect HBase rules that are available to you, use the Records Explorer.


Connect HBase rules are available in applications that have access to the functionality provided by the Pega-BigData ruleset.

Before you can connect to Apache HBase data store, upload the HBase client jars into the application container with the Pega Platform. You need different jars for particular versions of Apache HBase data store, so the jars are not in the Pega Platform database.

To create Connect HBase rules directly in your application, click Create Integration-ConnectorsConnect HBase.

Where referenced

Connect HBase rules can be referenced in activities.


A Connect HBase rule is an instance of the Rule-Connect-HBase rule type. Connect HBase rules belong to the Integration-Connectors category.

  • Previous topic Connect EJB form - Completing the Create tab
  • Next topic Connect HBase rules - Completing the Create, Save As, or Specialization form

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us