Release Notes for IDMC
- Release Notes for IDMC
- All Products
Issue | Description |
|---|---|
SCAN-24398 | When you use an underscore in a
metadata extraction filter, additional schemas that
don’t match the filter get extracted. This issue
occurs because in SQL the underscore (_) matches any
single character. |
SCAN-26566 | If you configure metadata extraction filters to exclude stored
procedures, tasks, pipes, and dynamic tables, you cannot
view the row count value in the system attributes.
|
Issue | Description |
|---|---|
CDGC-78928 | When you perform connection assignment to reference source systems,
the job succeeds but the number of matched and unmatched
objects doesn't match the number of extracted objects.
|
Issue
| Description
|
|---|---|
SCAN-17398
| Metadata extraction jobs don't parse the JavaScript function and the following error occurs:
com.compactsolutionsllc.cdimc.common.visitor.tracking.TrackedException: Parse error (NoViableAlt) on token: '.' . Line.column: 9.4, Text: [ >.<Array.from]
|
Issue
| Description
|
|---|---|
SCAN-13820
| When you import a session from a Snowflake.Snowpark library into a stored procedure, the metadata extraction job doesn't extract statement assets. The following error appears in the scanner debug log file:
|
SCAN-13841
| If a stored procedure uses the
snowflake.snowpark.Session.write_pandas() function to write
pandas DataFrame to a table in the source system, the metadata extraction job does not extract statement assets.
|
SCAN-13840
| If a stored procedure uses the
DataFrame.to_snowpark_pandas() function to convert
Snowpark pandas DataFrame
or Series
into
Snowpark DataFrame , the metadata extraction job doesn't extract statement assets. The following error appears in the scanner debug log file:
|