Resetting the Data Store

The clearMdex and provisionMdex operations of the Data Ingest Web Service are intended to be used together for removing the data and configuration from the Data Store while keeping the Dgraph process of the data store running on the Oracle Endeca Server. Running these operations implies that you have exported the configuration and will import it, after clearing and provisioning the data store.

Note: Clearing the data store without provisioning it again leaves the data store in an invalid state, preventing all further operations, including importing the configuration.

In a typical scenario, clearMdex is run as part of updating an existing data store without having to stop the Dgraph process or remove the configuration. This scenario implies that you export your configuration, remove all data and configuration records with clearMdex, provision the data store with provisionMdex, and import the configuration.

It is useful to note the difference between the clearMdex operation and the deleteRecords element in the ingestRecords operation of the Data Ingest Web Service (since both of these options let you delete records):

While you can send these operations directly to the data store, both of these operations are utilized by the Reset Data Store connector in Integrator. The connector is used for removing the records and the configuration from the data store and provisioning the data store while keeping the Dgraph process for the data store running. For more information on the connector, see the Oracle Endeca Information Discovery Integrator Components Guide.

It is recommended to run clearMdex and provisionMdex in conjunction, using the Reset Data Store connector in Integrator. In addition, it is recommended to run these operations within an outer transaction. You can start an outer transaction through the Transaction RunGraph connector in Integrator.