HBase is Required

Beginning with the Tamr v.2019.019, HBase is required when you deploy Tamr. Enable HBase and migrate datasets to it.

To enable HBase:

1. Upgrade to Tamr version 2019.019 or greater.
2. Set the TAMR_HBASE_ENABLED configuration variable in the admin-unify.sh admin tool to true. This also requires restarting Tamr and its dependencies. For information about using unify-admin.sh, see Configuring Tamr.

To migrate existing datasets to HBase:

1. Verify that the TAMR_HBASE_ENABLED configuration variable in the admin-unify.sh admin tool is set to true. See Configuring Tamr.
2. Convert existing datasets to HBase using the /datasets/moveDatasetsToStorageDriver API. For example, use this URL:

`http://<your-tamr-host>:9100/api/dataset/datasets/moveDatasetsToStorageDriver?destinationDriver=hbase` 

Alternatively, use this command:

`curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' 'http://<your-tamr-host>:9100/api/dataset/datasets/moveDatasetsToStorageDriver?destinationDriver=hbase'`. 

It starts a job that registers all datasets with HBase. To see which datasets are stored in HBase, use /datasets/<name>/status.
3. Set the TAMR_HBASE_AS_PRIMARY_STORAGE configuration variable in the admin-unify.sh admin tool to true. This ensures that going forward, all datasets are stored in HBase by default. See Configuring Tamr.