Deploying Enterprise Data Catalog on an embedded cluster running on SuSE Linux Enterprise 12 fails.

Enterprise Data Catalog displays incomplete lineage and impact information in the Compact view for a tabular asset that contains public synonyms.

After you run an Informatica Data Quality resource to extract the profile results, Catalog Administrator does not display associated resource reference objects in the

Reference Resources

section.

The Informatica Platform resource metadata extraction fails for the following target versions because of the new scanner binaries:

10.0
10.1
10.1.1
10.2 HF1

Metadata fetch fails for parquet files with

java.lang.UnsupportedOperationException

error on the HDFS resource.

Metadata fetch fails with

Failed to read input file: >>>NEED_WHOLE_FILE

error if the parquet file size exceeds 15 MB.

The Catalog Service fails with the following error for an Oracle resource when the resource and database share the same name:

When you drill down on a seed asset to display the child assets in the lineage and impact view, Enterprise Data Catalog displays incomplete lineage and impact information. This issue occurs for a non-administrator user that does not have the required permissions to view the assets.

You might not view all the intermediate assets in the lineage and impact view when you use the sliders to expand the view.

The Apache Kafka resource takes 26 seconds to determine the schema when the sampling size is more than 30 messages.

Deleting an Informatica Data Quality resource fails with an

OutOfMemory

error.

When you run a profile on XML files for the HDFS resource, the Data Transformation Manager stops with an out of memory exception.

The column level lineage is broken for an Apache Kafka resource, when you extract metadata from topics that contain hierarchical JSON messages related to streaming mappings.

The column level lineage is broken for an Apache Kafka resource, when you extract metadata from topics that contain hierarchical XML messages related to streaming mappings.

The lineage displayed for the Qlik Sense resource is incorrect when a column name in the Qlik Sense data source contains a slash (/).

Profile run fails on the Spark engine if a source table name or column name contains special characters.