Issue | Description |
|---|---|
SCAN-37448 | When you run a metadata extraction job, the job fails if the filter includes unlinked datasets. |
SCAN-36248 | When you run a metadata extraction job with filter patterns that contain certain characters, the job fails with a syntax error. |
SCAN-38195 | When you run metadata extraction for procedures that include the CURRENT_TIME() or FORMAT_TIME() functions, the job fails to generate lineage and the following error occurs: Cannot resolve CURRENT_TIME neither as a PL/SQL object nor type. |
SCAN-38517 | When you configure the catalog source to include table or view names with an underscore (_) in the metadata extraction filters, the metadata extraction job fails with the following error: Syntax error: Illegal escape sequence |
SCAN-38899 | When you configure the catalog source to include stored procedures in the metadata extraction filters, the metadata extraction job fails with a 404 Not Found error. This issue occurs because the job runs queries on datasets outside the location of the project specified in the connection. |
SCAN-34077 | When you run a metadata extraction job, the job can't parse views and fails with the following error: Parse error (NoViableAlt) on token: 'FROM' This issue occurs when the view definition uses the pipe query syntax. |
SCAN-39645 | If the source system has more than 100 projects, you cannot browse or filter objects of the catalog source. The filter browser fails to open and the following error message appears: Browsing catalog failed for ConnectionId: <connection_id>, CatalogSourceType: Google BigQuery, Location: []. Reason: Trying to return n elements from plugin GoogleBigQueryPlugin for location while pagination allowed for only 100 elements. Please check if your plugin correctly implements pagination. |
SCAN-37934 | When you run a metadata extraction job to extract metadata of stored procedures that use a whole-row table alias, such as SELECT TO_JSON_STRING(t) FROM S AS T, the job fails to generate lineage and the following error appears: UnsupportedOperationException. This issue occurs because whole-row aliases are not recognized as table references. |
Issue | Description |
|---|---|
CDGC-89007 | Data profiling tasks fail when you run the tasks on columns with names that contain spaces or special characters. This issue occurs when you choose the Limit N Rows sampling type. |
Issue | Description |
|---|---|
SCAN-20256 | When you run metadata extraction jobs on objects that include aggregate functions, the jobs fail with the following error: Failed to parse statement. Unable to parse script. |
SCAN-20342 | If a stored procedure contains a statement such as select (a, b) from c , the statement returns only one value instead of two. Since the value needs to be assigned to two variables, metadata extraction jobs fail with the following error: com.compactsolutionsllc.cdimc.common.visitor.tracking.TrackedException: Excessive SELECT INTO target at index 1. Number of available sources: 1 |