Help Center/ DataArts Studio/ FAQs/ DataArts Security/ Why Is "import jar to dws failed" Displayed in the Instance Execution Failure Log When a Sensitive DWS Data Discovery Task Fails?
Updated on 2026-03-20 GMT+08:00

Why Is "import jar to dws failed" Displayed in the Instance Execution Failure Log When a Sensitive DWS Data Discovery Task Fails?

Symptom

A sensitive DWS data discovery task fails, and error "import jar to dws failed" is displayed in the instance execution failure log.

Possible Causes

Hybrid transaction/analytical processing (HTAP) DWS clusters do not support user-defined functions (UDFs). Therefore, UDFs defined in DataArts Security for sensitive data discovery cannot be imported to DWS.

Solution

Use an online analytical processing (OLAP) DWS cluster to perform a sensitive data discovery task.

Use the SQL editor on the DWS management plane or run the select gs_extend_library('ls','') command in the DWS SQL script in DataArts Factory to check whether the cluster is an HTAP cluster. The cluster is an HTAP cluster and does not support sensitive data discovery tasks if the command output is as follows: ERROR: [53101] : This interface is not supported in htap cluster. Where: referenced column: gs_extend_library.