Known issues and limitations - Data360_Analyze

Known issues and limitations - Data360_Analyze - 3.12

Data360 Analyze Server Help

Product

Data360 Analyze

Version

3.12

Language

English

Portfolio

Verify

Product family

Data360

Product name

Data360 Analyze

Title

Data360 Analyze Server Help

2023

First publish date

2016

We would like to make you aware of the following list of issues and limitations.

If you encounter any other technical issues, contact support at support.precisely.com.

Third parties

The following table lists third party known issues and limitations:

Feature	Description
Avro	The Avro 1.7.7 specification lists some supported metadata constraints. Specifically, it places restrictions on the names of fields, as follows: The field names must start with [A-Za-z_] The field names must only contain [A-Za-z0-9_] Avro 1.7.7 does not support date, time and datetime data types. As a result, if you want to upload data and use the Data360 Analyze nodes, these fields will need to be converted to string data types.
Hadoop Hive Cluster	When downloading files from the Hadoop Hive Cluster, the WebHDFS API automatically encodes files to base64 format. As a result, it is not always possible to view the contents of the download in the fields on the output. For example, if the DataOutputMode property is set to Field, due to the automatic base64 encoding, the encoded result will be visible instead of the contents. To view the contents, set the DataOutputFieldEncoding property to None. However, this is not always possible due to invalid characters in the original file; in this case, the workaround is to set the DataOutputMode to File and then import the data using one of the input connector nodes.

Feature

Description

Avro

The Avro 1.7.7 specification lists some supported metadata constraints. Specifically, it places restrictions on the names of fields, as follows:

The field names must start with [A-Za-z_]
The field names must only contain [A-Za-z0-9_]

Avro 1.7.7 does not support date, time and datetime data types. As a result, if you want to upload data and use the Data360 Analyze nodes, these fields will need to be converted to string data types.

Hadoop Hive Cluster

When downloading files from the Hadoop Hive Cluster, the WebHDFS API automatically encodes files to base64 format. As a result, it is not always possible to view the contents of the download in the fields on the output.

For example, if the DataOutputMode property is set to Field, due to the automatic base64 encoding, the encoded result will be visible instead of the contents.

To view the contents, set the DataOutputFieldEncoding property to None. However, this is not always possible due to invalid characters in the original file; in this case, the workaround is to set the DataOutputMode to File and then import the data using one of the input connector nodes.

Web application

The following table lists Data360 Analyze known issues and limitations:

Feature	Description
Composite library nodes created in previous versions	When importing or running a data flow that was created in an older version of the product, you may see error messages if the data flow contains composite library nodes that have been upgraded since the data flow was first created. If the data flow did not previously show these errors, you can resolve the issues as follows: Open the data flow and select all nodes. Choose Apply Auto-Fixes. Save the data flow, then return to the Directory before reopening the data flow.
Links from tooltips to help	Although it is not currently possible to open the integrated help from the links in node property tooltips, you can manually navigate to the help by pressing F1 then searching for the relevant topic.
Logistic Regression node	The Logistic Regression node does not support Unicode for categorical data.
Output Tableau (Superseded) node	The Output Tableau (Superseded) node, which is now deprecated, has issues on a Linux installation of Data360Analyze when configured to upload files to a Tableau Server.