Customizing watsonx.data components

Customizing watsonx.data components involves updating various properties and configurations to suit your project requirement.

About this task

A project administrator can customize the properties for different watsonx.data components. For more information about different components and their properties, see Customizing components.

Note: If a particular property is not run successfully, the default value from the t-shirt size is picked. The new deployment configuration is implemented in a rolling update.

Procedure

To customize watsonx.data components such as MinIO, Postgres, Query History Monitoring and Management (QHMM), CES (Cloud Event Service), Metadata Service (MDS), Common Policy Gateway (CPG), and Content Aware Storage(CAS), complete the following steps:
1. Determine which watsonx.data component you need to customize.
2. Use the oc patch command to directly update a property and its value:
```
oc patch wxd/lakehouse --type=merge -n ${PROJECT_CPD_INST_OPERANDS} -p '{ "spec": { "<property_name>": "<value>" } }'
```
  Example
```
oc patch wxd/lakehouse --type=merge -n ${PROJECT_CPD_INST_OPERANDS} -p '{ "spec": { "minio_resources_requests_memory": "750Mi" } }'
```
3. Use the oc edit command to add or delete watsonx.datacomponent properties to the spec in the custom resource:
```
oc edit wxd lakehouse
```
4. Wait for a few minutes for the rolling update to take effect after you save the properties.
To customize the Engine components such as Presto (Java) worker, Presto (Java) singlenode, Presto (C++) worker, Presto (Java) coordinator, Catalog, etcd, and Kafka properties, complete the following steps:
1. Determine which Engine component you need to customize.
2. Run the oc get command to get the engine name:
```
oc get wxdengine
```
3. Use the oc patch command to directly update an engine property and its value:
```
oc patch wxdengine/<engine_name> --type=merge -n ${PROJECT_CPD_INST_OPERANDS} -p '{ "spec": { "<property_name>": "<value>" } }'
```
  Example
```
oc patch wxdengine/lakehouse-presto-01 --type=merge -n ${PROJECT_CPD_INST_OPERANDS} -p '{ "spec": { "presto_worker_replicas": "2" } }'
```
4. Use the oc edit command to add or delete engine properties to the spec in the custom resource:
```
oc edit wxdengine <engine_name>
```
5. Wait for a few minutes for the rolling update to take effect after you save the properties.
6. Monitor the status of the Presto engine to complete the configuration update.
```
watch "oc get wxdengine --namespace ${PROJECT_CPD_INST_OPERANDS}"
```
  When the Presto engine finishes applying the configuration update, the status of the RECONCILE column in the command output changes from InProgress to Completed.
7. If necessary, restart pods to apply the updated properties:
```
oc delete -n ${PROJECT_CPD_INST_OPERANDS} $(oc get pod -n ${PROJECT_CPD_INST_OPERANDS} -o name | grep presto)
```
  Note: Restarting pods is necessary only for the properties where restart is set as Y.
To customize the Addon components, complete the following steps:
1. Determine which Addon component you need to customize.
2. Use the oc patch command to directly update the property and its value:
```
oc patch wxdAddon/wxdaddon --type=merge -n ${PROJECT_CPD_INST_OPERANDS} -p '{ "spec": { "<property_name>": "<value>" } }'
```
  Example
```
oc patch wxdAddon/wxdaddon --type=merge -n ${PROJECT_CPD_INST_OPERANDS} -p '{ "spec": { "ingest_api_resources_requests_cpu": "2" } }'
```
3. Use the oc edit command to add or delete properties to the spec in the custom resource:
```
oc edit wxdAddon/wxdaddon
```
4. Wait for a few minutes for the rolling update to take effect after you save the properties.