Known issues and limitations for watsonx.data intelligence

The following issues and limitations apply to watsonx.data intelligence.

Known issues and limitations

Known issues for unstructured data governance

The following issues apply to the unstructured data governance feature:

In flows where a single document class is selected, classification and extraction might not work

Applies to: 2.4.0

In a flow where only one document class is provided for processing, the documents might not be properly processed.

In the Unstructured Data Integration flow, the Classification operator or Extract operator might fail to classify the documents or extract any entities respectively.

In unstructured data curation, the analysis flow might properly classify the documents. However, when you run the processing flow, the metrics might show that the documents were skipped for extraction or no entities were extracted.

Workaround: Manually update the generated flow:

  1. Replace the Classification operator with an Extract operator, and select all document classes.
  2. Remove any additional Extract operators that appear later in the flow.
Names of document class fields or field sets can't contain spaces

Applies to: 2.4.0

When you add a new field or field set to a document class and specify a name that contains one or more spaces, the field or field set is not created and the following error message is shown:
Update failed
The document class fields could not be updated. Try again later. Error details: Document class schema failed with the following error 'Document class validation failed: /document/fields/12/name: does not match the regex pattern ^\S+$; '

Workaround: Use names without spaces.

Known issues for data lineage with the watsonx.data intelligence service

Imported lineage mappings don't appear in the UI
Applies to: 2.4.0
The Add to catalog > Lineage mapping option is available, but after the import, the lineage mappings don't appear in the data lineage UI. You can use the lineage mapping option only if you have business lineage with IBM Knowledge Catalog..
The View lineage button does not redirect to the lineage graph

Applies to: 2.4.0

When you review the Db2, Oracle, Teradata, or watsonx.data assets in projects and catalogs, and click the View lineage button, you are not redirected to the lineage page.

Workaround: Search for the asset and open the lineage graph on the Data > Data lineage page.