Known issues and limitations for Common core services

The watsonx.data Presto connector may return with an error when accessing data

Applies to: 5.3.0

The watsonx.data Presto connector may return the following error when using the Presto C++ engine to query data:

sortedCandidates is null or empty for ModularHashingNodeProvider

Workaround: Restart the Presto C++ engine worker pods.

Delta Lake catalog can have columns with incorrect decimal precision

Applies to: 5.4.0

When creating a Delta Lake table, you can set the decimal precision for the table too high and the write job will accept the precision value. However, when you try to read this table later, it will not be able to read it.

It might show the following error:

ERROR BrowsingService.getAssets: Unable to retrieve data: The assets request failed: CDICO9999E: Internal error occurred: SCAPI error: Columns could not be obtained: Executing query failed with error: presto: query failed (200 OK): "Illegal argument error: Invalid precision and scale combo (100, 0). They should be in the range [0, 38] and scale can not be more than the precision."

Workaround: Set the decimal precision value to be in the range of 0 to 38.

Error for Oracle connections when running queries that contain user-defined data types (UDTs)

Applies to: 5.4.0

If you run an SQL query on a table or a view with columns that contain user-defined data types (UDTs), you might receive an error that contains this message:

[IBM][Oracle JDBC Driver]User defined type not found

The driver requires access to the metadata associated with the user-defined type (UDT) during the query execution. If you only have the SELECT privilege for the table, but you do not have the corresponding privilege for the UDT, the driver cannot access the UDT's metadata.

Workaround: Grant the necessary privilege to the UDT. For example:
GRANT EXEC ON TYPE::[schema].[typename] TO [User];

The ccs-cr custom resource might get stuck in In Progress status when Portworx storage is full

Applies to: 5.4.0

If Portworx storage is full on all worker nodes for two hours or more, the ccs-cr custom resource can get stuck in In progress status. This is caused by the rabbitmq pods continuously restarting. However, no obvious error is logged in the rabbitmq pod logs.

Workaround: Manually trigger recovery of the rabbitmq pods:

1. Scale down rabbitmq-ha statefulset to 0 replicas:

   oc scale sts/rabbitmq-ha --replicas=0
   

2. Delete the rabbitmq-ha PVCs:

   oc delete pvc -l icpdsupport/module=rabbitmq-ha
   

3. Scale up rabbitmq-ha statefulset to 3 replicas

   oc scale sts/rabbitmq-ha --replicas=3
   

After the rabbitmq statefulset is up, the rabbitmq pods start successfully and the ccs-cr moves to the Completed status.

The ccs-cr does not reconcile after updating the common core services custom resource (ccs-cr)

Applies to: 5.3.1

After updating the ccs-cr with the oc patch command, the CCS custom resource does not reconcile. The CCS custom resource shows the updates, but it does not automatically trigger reconciliation.

Workaround: Run the following command to patch the ccs operator to increase the /tmp disk size.

   oc patch deployment ibm-cpd-ccs-operator --type='json' -p='[
  {
    "op": "replace",
    "path": "/spec/template/spec/containers/0/resources/limits/ephemeral-storage",
    "value": "5Gi"
  },
  {
    "op": "replace",
    "path": "/spec/template/spec/containers/0/resources/limits/memory",
    "value": "5Gi"
  },
  {
    "op": "replace",
    "path": "/spec/template/spec/volumes/0/emptyDir/sizeLimit",
    "value": "5Gi"
  },
  {
    "op": "replace",
    "path": "/spec/template/spec/volumes/1/emptyDir/sizeLimit",
    "value": "5Gi"
  },
  {
    "op": "replace",
    "path": "/spec/template/spec/containers/0/resources/requests/ephemeral-storage",
    "value": "5Gi"
  }
]'

User groups are not fully displayed on the Access Control tab

Applies to: 5.4.0

When you open the Connectivity Access Control tab for the first time, the tab does not display all user groups and only shows a partial list of catalog collaborators.

Workaround: To view the full list of user groups, choose one of the following options:

• Open the Add collaborators tab. After closing it, the full list displays.
• Go to Catalogs and open Catalog details > Access tab.

IBM watsonx.data Presto connector does not support specific data types when reading Data Lake tables.

The watsonx.data Presto connection does not support TIME and TIMESTAMP data types when reading Data Lake tables. It might show the following error:

Invalid time zone key

IBM watsonx.data Presto connector can't write to watsonx.data as a Service

The IBM watsonx.data Presto connector cannot write to IBM watsonx.data as a Service Lite in version 2.3.

IBM watsonx.data Presto connector can not write to S3 storage when using IAM role authentication

In watsonx.data you can connect to S3 storage using the IAM role authentication method. The watsonx.data Presto will not be able to write data to the catalog associated with that storage.

Disabling SSL certificate validation requires extra steps

If users want to explicitly disable the SSL certificate validation, users will have to perform extra steps to ensure that it has been disabled.

Procedure
When creating a new connection or editing an existing connection in the user interface:

1. Select the option to Validate the SSL certificate.
2. Unselect the option to Validate the SSL certificate.
3. Save the connection.

This will need to be performed for any connection where users want to disable the SSL certificate validation.

The watsonx.data and Presto connections do not work with specific data types

Applies to: 5.3.0

The watsonx.data Presto and Presto connections currently do not work with the following data types:

• TIME

The TIME and TIMESTAMP data types are not supported when the Presto C++ engine is used.