What's new and changed in Watson Knowledge Catalog

Installing or upgrading Watson Knowledge Catalog

Cloud Pak for Data Version 4.6.5

A new version of Watson Knowledge Catalog was released in April 2023 with Cloud Pak for Data 4.6.5.

Operand version: 4.6.5

This release includes the following changes:

New features

The 4.6.5 release of Watson Knowledge Catalog includes the following features and updates:

Run data quality rules on additional data sources

You can now run data quality rules on data assets from the following data sources:

• Amazon S3
• Apache Cassandra
• Databricks connected through Generic JDBC
• SAP ASE
• SAP HANA

For details, see Supported data sources for metadata import, metadata enrichment, and data quality rules.

Easier recovery from errors that happen during the initial synchronization with the data mart

If the synchronization for a particular item fails, the metadata related to them is not synchronized to the target tables in the data mart. Instead, this data item is skipped until you resolve the underlying problem.

After you resolve the issue that triggers the error, the details of that missing asset or artifact in the data mart are updated. For example, if a connection is missing some required fields, the synchronization of the connection is completed after you add the missing data.

In addition, whenever you change the reporting configuration, all the assets that were skipped during the initial synchronization will be queued for an update.

For details, see Starting, stopping, pausing, and resuming reporting for Watson Knowledge Catalog.

Updates

The following updates were introduced in this release:

• You can now select additional content for output links in data quality rules. For more information, see Creating rules from data quality definitions.
• In metadata enrichment, you can now run in-depth key analysis to identify key relationships between data assets. For more information, see Identifying relationships.

Customer-reported issues fixed in this release

Catalogs

DT211264: Results overlap when searching for business terms.

Data Curation

DT211268: Unable to run profiling on Apache Hive data source using Kerberos authentication.

DT211282: Manually assigned data classifications and business terms are removed from a catalog asset if the asset is published to the same catalog using metadata enrichment.

DT211716: When row filtering is used as data protection action, the asset profile still shows the excluded data on the Profile tab and deep drill downs.

General

DT203364: Can't change the default probe timeout value with IIS Solr component.

DT208292: Unable to import Microsoft Azure Data Lake Store Gen 2 connector files that are partitioned by key.

Governance artifacts

DT211716: Row filtering not applied to asset profile.

Security fixes

CVE-2023-0215, CVE-2023-0286, CVE-2023-22608, CVE-2023-23916, CVE-2023-24998, CVE-2023-25153, CVE-2023-25173, CVE-2023-25586, CVE-2023-27320

CVE-2022-1280, CVE-2022-2047, CVE-2022-2048, CVE-2022-21476, CVE-2022-23471, CVE-2022-23709, CVE-2022-24823, CVE-2022-25844, CVE-2022-25869, CVE-2022-25901, CVE-2022-25927, CVE-2022-31030, CVE-2022-31160, CVE-2022-32149, CVE-2022-3324, CVE-2022-34169, CVE-2022-3491, CVE-2022-3521, CVE-2022-36944, CVE-2022-3715, CVE-2022-3736, CVE-2022-37601, CVE-2022-3924, CVE-2022-4141, CVE-2022-41721, CVE-2022-41723, CVE-2022-41881, CVE-2022-41915, CVE-2022-4304, CVE-2022-4379, CVE-2022-43995, CVE-2022-4450, CVE-2022-4492, CVE-2022-4543, CVE-2022-47024, CVE-2022-48285,

CVE-2021-20264, CVE-2021-21290, CVE-2021-21295, CVE-2021-21409, CVE-2021-22132, CVE-2021-22134, CVE-2021-22144, CVE-2021-25740, CVE-2021-3701, CVE-2021-3702, CVE-2021-37136, CVE-2021-37137, CVE-2021-4041, CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, CVE-2021-43797, CVE-2021-44568

CVE-2020-14422, CVE-2020-7021, CVE-2020-7662, CVE-2020-8244, CVE-2020-8565

CVE-2019-10202, CVE-2019-11250, CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2019-4304, CVE-2019-4305

CVE-2018-1553, CVE-2018-1683, CVE-2018-1851

CVE-2017-0663, CVE-2017-14166, CVE-2017-14501, CVE-2017-15412, CVE-2017-18258, CVE-2017-7375, CVE-2017-9047, CVE-2017-9048, CVE-2017-9049, CVE-2017-9050

CVE-2016-0378, CVE-2016-1000027, CVE-2016-4658, CVE-2016-5131

CVE-2014-0429, CVE-2014-0432, CVE-2014-0446, CVE-2014-0448, CVE-2014-0449, CVE-2014-0451, CVE-2014-0452, CVE-2014-0453, CVE-2014-0454, CVE-2014-0455, CVE-2014-0456, CVE-2014-0457, CVE-2014-0458, CVE-2014-0459, CVE-2014-0460, CVE-2014-0461, CVE-2014-0463, CVE-2014-0464, CVE-2014-1876, CVE-2014-2397, CVE-2014-2398, CVE-2014-2401, CVE-2014-2402, CVE-2014-2403, CVE-2014-2409, CVE-2014-2410, CVE-2014-2412, CVE-2014-2413, CVE-2014-2414, CVE-2014-2420, CVE-2014-2421, CVE-2014-2422, CVE-2014-2423, CVE-2014-2427, CVE-2014-2428, CVE-2014-3488

CVE-2013-0169

Cloud Pak for Data Version 4.6.4

A new version of Watson Knowledge Catalog was released in March 2023 with Cloud Pak for Data 4.6.4.

Operand version: 4.6.4

This release includes the following changes:

New features

The 4.6.4 release of Watson Knowledge Catalog includes the following features and updates:

Adding relationships between assets and artifacts

Now, you can add and manage relationships between catalog assets and governance artifacts.

For example, you can identify which rules an asset adheres to by adding a previously defined custom relationship, such as Adheres to, between an asset and the classification.

To learn more about relationships, see Asset relationships in catalogs.

Create queries, reports, or dashboards based on custom relationships

When you create custom relationships between assets and governance artifacts, the relationships are synced to Watson Knowledge Catalog reporting data mart, so that you can create reports.

For example, you can use the custom relationships reporting to:

• Obtain quality analytics at various levels of granularity (by domain, by metadata, by user, by team)
• Certify the data quality of your data
• Count the number of assets that have a specific privacy property

To learn how to create custom relationships, see Custom properties and relationships for governance artifacts and catalog assets.

To learn how to create reports, see Setting up reporting for Watson Knowledge Catalog.

View custom relationships on lineage graph

You can now view custom relationships between assets as lineage flows in the lineage graph. For details, see Exploring business lineage.

Define a composite key for a reference data set

You can now specify multiple columns to create a composite key for your reference data sets. Without a composite key, reference data values in a set are identified by a unique string in the code column. A composite key is a combination of the code column and up to 5 custom columns in a reference data set.

A composite key is used to uniquely identify each reference data value. With a composite key, the values in the code column no longer need to be unique. Uniqueness is guaranteed only when the values of all the specified columns are combined. For details, see Designing reference data sets.

Drill down into the details of profiling results

You can now access detailed profiling information from within a metadata enrichment or from an asset’s Profile tab in a project or a catalog. For each column, view statistical information about the column data, information about data classes, data types and formats, and the frequency distribution of values in the column. For the statistical information, you can also choose between several types of visualizations.

For details, see Column-level profile details.

Import lineage from additional data sources

You can now run metadata imports to get lineage data from Amazon Redshift data sources. For details, see Supported data sources for metadata import, metadata enrichment, and data quality rules.

Run data quality rules on additional data sources

You can now run data quality rules on data assets from the following data sources:

• Watson Query
• Microsoft Azure Data Lake Store
• Snowflake

For details, see Supported data sources for metadata import, metadata enrichment, and data quality rules.

Run advanced analyses on enriched assets

When you run metadata enrichment, you can run the following analyses:

Primary key analysis

You can run a primary key analysis to detect primary keys in your data that uniquely identify each record in a data asset. For details, see Identifying primary keys.

Relationship analysis

You can run a relationship analysis to identify relationships between data asset or to find overlapping and redundant data in columns. For details, see Identifying relationships.

New option for binding variables in data quality rules

You can now use job parameters to bind rule variables to data columns and manage those parameters centrally in a project. With this option, you no longer need to update the rules when you want to change the binding to a different column. For details, see Creating rules from data quality definitions.

Updates

The following updates were introduced in this release:

• You can now assign governance rules to data quality rules in projects.

Customer-reported issues fixed in this release

Governance artifacts

DT208669: Reference data UI does not display reference data set details due to missing reference data relationship details

Reporting

DT208665: Reporting not working for categories with reference data sets with composite keys

Security fixes

CVE-2023-0687, CVE-2023-21830, CVE-2023-21843, CVE-2023-23931

CVE-2022-2153, CVE-2022-2873, CVE-2022-3586, CVE-2022-37454, CVE-2022-3996, CVE-2022-40897, CVE-2022-41222, CVE-2022-42919, CVE-2022-43945, CVE-2022-4415, CVE-2022-47629, CVE-2022-48303

Cloud Pak for Data Version 4.6.3

A new version of Watson Knowledge Catalog was released in February 2023 with Cloud Pak for Data 4.6.3.

Operand version: 4.6.3

This release includes the following changes:

New features

The 4.6.3 release of Watson Knowledge Catalog includes the following features and updates:

Metadata import enhancements

New options for metadata import

To ensure that the project or catalog where you are importing metadata doesn't contain stale data, you can specify which assets are deleted when you rerun the import. You can choose to delete the following types of assets:

• Assets that are no longer available in the data source.
• Assets that were removed from the import scope.

For details, see Importing metadata.

Import from additional data sources

You can now run metadata import on the following connections to discover data:

• Amazon Redshift
• FTP

For details, see Supported data sources for metadata import, metadata enrichment, and data quality rules.

Metadata enrichment changes and enhancements

New enrichment settings for term assignment

For each project, you can choose whether term rejections should be considered when the confidence score for a term assignment or suggestion is calculated. When this option is enabled, the confidence values of all selected term assignment values are adjusted.

In addition, you can set the training scope for the machine learning models that are used in the project without selecting the machine learning method for term assignment. Depending on the project settings, the training scope applies to one or both of the following models:

• The build-in model for term assignment
• The model for adjusting scores

For details, see Default enrichment settings.

Test model configuration

When you set up metadata enrichment to use a custom service for automatic term assignment, you can now test the service configuration. For details, see Adding a custom service for automatic term assignment.

New features for data quality rules in projects

Use more than one data quality definition in a single data quality rule

You can now use more than one data quality definition to build your rule. In addition, you can include an individual definition more than once to apply the same definition to different columns. For details, see Creating rules from data quality definitions.

Download rule output as CSV file

If an output table is defined for a rule, you can also download the rule output as a CSV file from the run history. This enables you to work with the output in other programs, such a spreadsheet program, especially if you want to search and filter output that contains a large number of records. For details, see Checking the run history.

Export and import data quality information

When you export a project, you can now include data quality assets. For details, see Exporting a project.

In addition, you can now export and import data quality assets by using the IBM Cloud Pak for Data export and import utility (the cpd-cli export-import command). For details, see Migrating catalog assets.

Run rules on data from additional data sources

You can now run data quality rules on data from the following data sources:

• Amazon Redshift
• Greenplum

For details, see Supported data sources for metadata import, metadata enrichment, and data quality rules.

Send reporting data to Oracle databases

When you send your Watson Knowledge Catalog data to an external database to generate reports, you can now choose an Oracle database, in addition to PostgreSQL and Db2® databases. For details, see Setting up reporting on Watson Knowledge Catalog.

Manage custom relationships with the Watson Knowledge Catalog APIs

Create and manage custom relationships between governance artifacts and assets from projects, catalogs, and spaces with the Watson Knowledge Catalog APIs.

Capture lineage for existing catalog assets with the Watson Knowledge Catalog APIs

Lineage can now be calculated for custom assets that existed in a catalog before the lineage feature was enabled. Use the Watson Data APIs to generate and load existing asset lineage information. For more information on bulk loading assets, see Exploring business lineage.

Monitor authoring tasks

Authoring tasks for governance artifacts are now shown in task inbox and the Task status page. When a category collaborator creates a draft for a governance artifact, all category collaborators with roles Owner, Admin, or Editor can see a new Authoring task in their task inbox. If you claim an authoring task, it disappears from others' inboxes. For more information, see Authoring task type.

Updates

The following updates were introduced in this release:

• The Access data quality asset types permission is now part of the Data Quality Analyst role's default permission set.
• The data quality assets now have an About side panel that provides further details about the definition or the rule, such as related assets.
• You can now export and import data quality assets from and to projects and catalogs.
• Information about supported data sources for metadata import, metadata enrichment, and data quality rules is now available in a single table. See Supported data sources for metadata import, metadata enrichment, and data quality rules.

Customer-reported issues fixed in this release

Data curation

DT196691: Profiling assets fails when enrichment is being run.

DT196689: After installing Watson Knowledge Catalog 4.6.0, the Ready value for the wkc-data-rules pod remains at 0/1 (not ready) and never becomes 1/1 (ready).

General

DT180666: Open Data for Industries services go offline and settings are overwritten when running patch for HTTPS.

Governance artifacts

DT196688: Cannot delete Watson Knowledge Catalog reference data in bulk.

DT196692: Error messages are returned in Simplified Chinese instead of Traditional Chinese.

Security fixes

CVE-2022-0396, CVE-2022-1304, CVE-2022-21619, CVE-2022-21624, CVE-2022-21626, CVE-2022-21628, CVE-2022-24999, CVE-2022-2509, CVE-2022-25168, CVE-2022-25169, CVE-2022-26336, CVE-2022-27404, CVE-2022-27405, CVE-2022-27406, CVE-2022-27664, CVE-2022-28389, CVE-2022-2879, CVE-2022-2880, CVE-2022-2964, CVE-2022-30126, CVE-2022-30973, CVE-2022-3204, CVE-2022-32189, CVE-2022-3324, CVE-2022-33879, CVE-2022-33980, CVE-2022-3435, CVE-2022-3515, CVE-2022-3522, CVE-2022-35737, CVE-2022-3621, CVE-2022-36364, CVE-2022-3649, CVE-2022-37434, CVE-2022-3821, CVE-2022-38900, CVE-2022-3910, CVE-2022-39135, CVE-2022-40151, CVE-2022-40153, CVE-2022-40303, CVE-2022-40304, CVE-2022-4139, CVE-2022-4141, CVE-2022-41715, CVE-2022-41716, CVE-2022-41854, CVE-2022-41940, CVE-2022-41946, CVE-2022-42010, CVE-2022-42011, CVE-2022-42012, CVE-2022-42889, CVE-2022-42898, CVE-2022-43548, CVE-2022-43680, CVE-2022-43995, CVE-2022-45146, CVE-2022-45868, CVE-2022-45873, CVE-2022-45888

CVE-2021-22573, CVE-2021-44906, CVE-2021-46848

CVE-2020-13790, CVE-2020-15522, CVE-2020-2801, CVE-2020-35525, CVE-2020-35527, CVE-2020-35538, CVE-2020-36518, CVE-2020-36557

CVE-2019-16866, CVE-2019-2201, CVE-2019-25033

CVE-2016-3709

CVE-2014-0107

Cloud Pak for Data Version 4.6.1

A new version of Watson Knowledge Catalog was released in December 2022 with Cloud Pak for Data 4.6.1.

Operand version: 4.6.1

This release includes the following changes:

New features

The 4.6.1 release of Watson Knowledge Catalog includes the following features and updates:

New features for data quality rules in projects

You have more options when you create data quality rules:

• When you create rules from data quality definitions, you can now choose to send output records to output links in the DataStage® flow instead of writing the records to a database. For details, see Creating rules from data quality definitions.
• You can quickly build custom data filters and data quality checks in rules by using SQL statements and run these rules on data sources that support SQL. For details, see Creating SQL-based rules.

Enhancements for asset and artifact definitions

Filter tables

You can filter governance artifacts, catalog assets and custom properties to find the item you're looking for faster.

Specify predefined values for custom properties on catalog assets

You can now create a custom property for an asset type that contains a set of predefined values. For details, see Custom properties and relationships for governance artifacts.

Bulk load lineage information to a lineage graph bulk

Starting in Version 4.6.1, you can use bulk load to synchronize large amounts of lineage data from a catalog to a lineage graph. You can use bulk load to synchronize the following information from assets in the catalog:

• Internal details (columns for database tables or views)
• Term assignments (for both assets and columns)
• Data flow information that is stored in the data_lineage attribute
• Referenced connections
• Assigned classifications

For details, see Exploring business lineage.

New Manage governance artifacts permission

You can now give users the Manage governance artifacts permission, which enables them to view all governance artifacts in all categories, regardless of whether the users are collaborators in those categories. With this permission, users can also run all API calls for governance artifacts.

You can combine the Manage governance artifacts with the following permissions to give users full control over category and governance artifacts:

• Manage categories
• Access governance artifacts

For details, see Predefined roles and permissions in Cloud Pak for Data.

Column metadata now available to all users

You can now view and manage column metadata for a data asset from the Overview tab for the asset. Even if you do not have access to the data due to a data protection rule, you can still view the column metadata for the asset.

Enhancements in workflow configuration and management

Configuration properties for custom workflows

In addition to configuration properties for tasks in a workflow, you can now define additional configuration properties for a workflow as a whole. Use these properties to provide values to the workflow logic, for example:

• Use a toggle to turn on or off some parts of a workflow.
• Provide an api_key or endpoint URL for calling external services.
• Provide threshold level for a decision taken by the workflow logic.
• Provide any other configurable value that is needed by the workflow logic.

You can define workflow configuration properties in the Flowable tool as described in Designing and creating custom workflows.

Task duration

You can now set duration period for each user task in a workflow. When the date is reached, the task is labeled as Overdue. For more information, see Designing and creating custom workflows.

Adding assignees

In the task status page you can now add new assignees to the tasks. This is a helpful feature to use if you need to unblock a task when the current assignee is not available to process it. You can also filter the task list for unassigned tasks and add assignees to them. For more information see Monitoring workflow tasks.

Updates

The following updates were introduced in this release:

• You can now import table or column level descriptions when using Microsoft SQL Server as a data source with metadata import.
• You can now sort and filter enrichment results by enrichment status.
• From the metadata enrichment results, you can now directly access the latest job run details for each asset.
• In case of profiling errors, you can now directly access the log of the profiling job from the metadata enrichment results.

Customer-reported issues fixed in this release

Data curation

DT178889: Data profiling creates a SYSTEM connection for a local asset file even if the connection already exists.

DT172215: Automatic profiling does not retry when it fails.

Security fixes

CVE-2022-0168, CVE-2022-0617, CVE-2022-0854, CVE-2022-1016, CVE-2022-1048, CVE-2022-1055, CVE-2022-1158, CVE-2022-1184, CVE-2022-1852, CVE-2022-20368, CVE-2022-2078, CVE-2022-21499, CVE-2022-23960, CVE-2022-2421, CVE-2022-24448, CVE-2022-2586, CVE-2022-2602, CVE-2022-26373, CVE-2022-2639, CVE-2022-28390, CVE-2022-28893, CVE-2022-2938, CVE-2022-29581, CVE-2022-31692, CVE-2022-3297, CVE-2022-3303, CVE-2022-36087, CVE-2022-36946, CVE-2022-37601, CVE-2022-37865, CVE-2022-37866, CVE-2022-38126, CVE-2022-38127, CVE-2022-38128, CVE-2022-39190, CVE-2022-39353, CVE-2022-40154, CVE-2022-40155, CVE-2022-40156, CVE-2022-42252, CVE-2022-42969

CVE-2021-25220, CVE-2021-30002, CVE-2021-33135, CVE-2021-3640, CVE-2021-4048

CVE-2020-36558, CVE-2020-36516

CVE-2018-16428

CVE-2015-20107

Cloud Pak for Data Version 4.6.0

A new version of Watson Knowledge Catalog was released in November 2022 with Cloud Pak for Data 4.6.0.

Operand version: 4.6.0

This release includes the following changes:

New features

The 4.6.0 release of Watson Knowledge Catalog includes the following features and updates:

Enhancements to metadata import

The following enhancements are available when you import metadata:

• You can now keep customized asset information when data is re-imported. For each metadata import configuration, you can specify whether assets names, asset descriptions, or column descriptions are updated whenever the data is re-imported. For details, see Discovering data.
• You can now import lineage information from Netezza® Performance Server data sources.

Customized term assignment and sampling in metadata enrichment

The following enhancements were made to metadata enrichment:

Customize ML-based term assignment

For each project, you can now specify whether your models for ML-based term assignment are trained from assets in the project or from a catalog.

If Watson Machine Learning is installed in your Cloud Pak for Data environment, you can create and use your own ML model for term assignment instead of the built-in model.

For details, see Default enrichment settings.

Capture data changes more accurately with improved sampling

When you set up customized sampling, you can choose between sequential and random sampling, if the data source supports random sampling. In addition, you can optionally choose to include a certain percentage of the table rows in the sample, rather than a fixed number of rows.

For details, see Enriching your data assets.

More options for binding variables in data quality rules

You can now use job parameters to bind a rule to literal values that are centrally managed in a project. Literal values can change at run time, by using job parameters, you don’t need to update the rule when values change.

For details, see Managing data quality rules.

Asset and artifacts definitions

With the new asset and artifacts definitions feature, you can create your own custom properties and relationships for glossary artifacts and catalog assets. Additionally, you can import and export custom property and relationship definitions for glossary artifacts. For details, see Custom properties and relationships for governance artifacts.

Enhancements to lineage graph

The lineage graph includes the following improvements:

• You can now track the flow of a node's cycles as well as its member, which helps provide more accurate and detailed data.
• The Show columns dialog has been reorganized so that you can more easily select the columns to show on the graph.
• You can now set your preferences for how to display the legend and the overview of a graph.
• The legend is now dynamic and displays only the most common asset types. You can see all your asset types that are in a graph by selecting.

For details, see Exploring business lineage.

Usability enhancement when creating governance artifacts

Now you can create a new category on the fly with the New category button. For example, when you create a governance artifact but you do not have access to any existing categories, or the categories that are available do not meet your requirements, you might want to define a new category without leaving the open window. For more information, see Managing categories.

New industry-specific data classes with Knowledge Accelerators

The Knowledge Accelerators extend the set of data classes provided in Watson Knowledge Catalog. The Knowledge Accelerators data classes:

• Are based on industry standards such as ISO, FHIR, and CIM.
• Describe commonly used information in data sources from industries such as Energy & Utilities, Financial Services, Healthcare, and Insurance.
• Define expected patterns in business data formats or leverage a known set of values from new and existing Knowledge Accelerators reference data sets

The data classes enhance the Watson Knowledge Catalog metadata enrichment process so that it can recognize industry-specific data. When the data classes are mapped to the Knowledge Accelerators glossary, metadata enrichment can automatically assign these discovered data assets to their respective business terms.

The data classes are fully customizable and can be adjusted to focus on client-specific reference data sets or column-name-matching restrictions.

For details, see Knowledge Accelerators.

View metadata of blocked assets in catalogs

Users who cannot access based on data protection rule can now see the metadata of the assets. For example, when users click on a blocked asset in a catalog they can now see the description, assigned terms, custom properties, relationships, and column names of the blocked asset.

For more information on how users can interact with data under a “deny access” data protection rule, see the action table in Designing data protection rules.

Extensive new query capabilities

You can now create custom reports on:

• Workflow data
• Metadata imports
• User profiling
• Metadata enrichment

For example, to ensure the quality of automatic term assignments for your discovered data sets and columns, you can generate a report to list the assigned and rejected terms for the data sets and columns.

To learn more about creating custom reports, see Setting up reporting for Watson Knowledge Catalog.

Show usernames and emails in reports

Now managers and reporting administrators can enable user profiling for a catalog in Reports setup. If you enable user profiling, user information such as emails and usernames are reported to the data mart along with the user ID. This information can be displayed in reports.

For more information, see Setting up reporting for Watson Knowledge Catalog

Easily access your activity history

Now you can easily access your activity history for projects and catalogs by clicking the View asset activities icon () in the action bar of an asset.

Updates

The following updates were introduced in this release:

• The Access data quality asset types permission is now included by default in the permission set of the Administrator role.

Customer-reported issues fixed in this release

Catalog

DT160645: After upgrading to 4.5, issues sometimes occur while scheduling profiling jobs.

DT160298: When switching the language to Turkish, the "All catalogs" page is displayed in German.

DT129073: Adjustments to discovery UI APIs takes a long time to fetch data.

DT170263: Watson Knowledge Catalog diagnostics job completes with an error and partial log collection.

Data curation

DT144597: Metadata enrichment publish may fail with "500 Internal Server Error" after Cloud Pak for Data cluster restarts.

DT173286: When running a term assignment for data classes in metadata enrichment, no terms are assigned on tables that have more than 10 columns with data classes assigned.

DT173266: No assets are imported if a metadata import for getting lineage from a Db2 or an Oracle data source has the connection selected as data scope.

DT173267: In IAM-enabled environments, lineage imports from Greenplum and PostgreSQL connections don’t work.

DT173588: Unable to schedule the data asset analysis task from a data quality project.

General

DT129073: Adjustments to discovery UI APIs takes a long time to fetch data.

DT170263: Watson Knowledge Catalog diagnostics job completes with an error and partial log collection.

Profiling

DT160645: After upgrading to 4.5, issues sometimes occur while scheduling profiling jobs.

• Updates to advanced data masking rule are not reflected when rule logic is changed or deleted

  Issue: When data masking vaulted assets and a rule configuration is deleted, updates to the advanced data masking rule are not reflected in the Assets tab of a dashboard to preview the asset.

  Resolution: This issue is now fixed.

• Issue: Masking flow jobs fail in the default Spark 3.2 environment

  Resolution: This issue is now fixed.

Security fixes

CVE-2022-0494, CVE-2022-0778, CVE-2022-1292, CVE-2022-1353, CVE-2022-1678, CVE-2022-1972, CVE-2022-2068, CVE-2022-2097, CVE-2022-21123, CVE-2022-21125, CVE-2022-21166, CVE-2022-2231, CVE-2022-2288, CVE-2022-2289, CVE-2022-2308, CVE-2022-23816, CVE-2022-23825, CVE-2022-2509, CVE-2022-2526, CVE-2022-25857, CVE-2022-2588, CVE-2022-25896, CVE-2022-2862, CVE-2022-2978, CVE-2022-2982, CVE-2022-29900, CVE-2022-29901, CVE-2022-3016, CVE-2022-30698, CVE-2022-30699, CVE-2022-3099, CVE-2022-34903, CVE-2022-36033, CVE-2022-39046

CVE-2021-25642, CVE-2021-3114, CVE-2021-4093, CVE-2021-4160, CVE-2021-46195, CVE-2021-46828

CVE-2020-16156, CVE-2020-35525, CVE-2020-35527

CVE-2019-11922, CVE-2019-16866, CVE-2019-25033, CVE-2019-5427

CVE-2018-20406, CVE-2018-20433