Page tree

 

Contents:


This section contains miscellaneous configuration topics to enable minor features of the platform.

Limits

For more information, see Configure Application Limits.

Configure CSV field delimiters

When you publish a CSV file, by default the fields in the file are comma-separated. Optionally, you can configure a different field delimiter.

Tip: During publication, you can specify whether the output file includes double quote marks around each field. For more information, see Run Job Page.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. To enable the feature, verify that the following parameter has been set to true:

    "feature.publishDelimiterQuoteOption.enabled": true,
  3. If you wish to specify the delimiter character using a Unicode value, please set the following to true:

    "feature.publishDelimiterQuoteOption.enableUnicodeCSVDelimiters": true,
  4. Search for the following parameter:

    "webapp.outputCsvDelimiter"
  5. In the textbox, enter the string that is used as the delimiter.
    1. Strings can be more than one character in length.
    2. If you have enabled the Unicode CSV delimiters feature, you can enter Unicode characters in the following format:

      \uXXXX

      where XXXX is the Unicode value for the character.

      NOTE: The delimiter value is used as the default value for each job. The default can be overridden on a per-job basis. For more information, see Run Job Page.

  6. Save your changes.

Supported Extensions

By default, the Trifacta® platform will allow you to upload any file. However, the platform may not be able to process some of them, as the list of supported file extensions is limited. For more information, see Supported File Formats.

When you upload a file with an unsupported file extension, a warning is displayed, and the file may fail to load in the Transformer page. 

As needed, you can add extensions to the list of supported file formats, so that no warning is displayed when a file of the specified type is imported. 

  • Extensions are case-sensitive. .xml and .XML must both be listed.
  • A leading period is required.

NOTE: The Trifacta platform prevents the uploading of files with extensions that are disabled through specific configuration flags. For example, if you disable BZIP2 or Avro files, you cannot re-enable them by adding their extensions to this configuration list.


Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Locate the following parameter and add file extensions. In the example, two new extensions have been added to the list:

    "webapp.client.additionalAllowedFileExtensions": [".log",".LOG"],
  3. Save your changes and restart the platform.

Feature Flags


Enable WebAssembly client

NOTE: This feature is in Beta release. However, if interested, you can enable WebAssembly for the Photon client. Some limitations apply. Please review below.

The Photon running environment on the Trifacta node requires the use of a client component in Google Chrome. The platform supports the following clients:

ClientNotes
PNaCl

This client is the default client used by the platform.

Support for PNaCl desktop client is likely to be deprecated in a future release. Please upgrade your Google Chrome browser to 68+.

This client requires additional installation and enablement on the individual desktops in the environment. For more information, see Configure Desktops.

WebAssembly

This client is the replacement for PNaCl. Beginning in Google Chrome 68, WebAssembly is available and enabled by default in the client.

NOTE: This feature is in Beta release.

NOTE: Google has indicated that PNaCl desktop client is being replaced by WebAssembly, which is a standards-compliant client supported by all major browsers. Even if you do not enable WebAssembly in this release, you should plan to upgrade all desktop to Google Chrome 68+.

Tip: Use of WebAssembly is recommended.

Limitations of WebAssembly:

In this release, the following limitations apply to use of WebAssembly:

  • The current implementation of WebAssembly in this release is single-threaded, and performance may be impacted. 
    • Google has not yet implemented multi-threaded WebAssembly. 
    • When multi-threading is available, the Photon implementation will feature multi-threading.
  • Custom UDFs are not available with WebAssembly.
  • Progress bars are not displayed for actions in the Transformer page. This is a known issue.

Enable WebAssembly in the platform:

If you would like to enable use of WebAssembly, please do the following.

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Locate the following parameter:

    "photon.mode": "pnacl",
  3. Set the above value to wasm.
  4. Save changes and restart the platform.

When the platform is restarted, all users connecting to the platform utilize their local desktop client for WebAssembly. No additional configuration is required.


Disable enforced type casting

For non-schematized outputs,  Trifacta Wrangler Enterprise enforces casting of all values to the annotated data type of the column by default. For example, if the output value is -3.4 and the data type for the output column is Integer, the platform enforces Integer type casting and writes a null value instead.

This behavior is governed by the following parameter: webapp.enableTypecastOutput

Parameter SettingDescriptionImplications on Mismatched Values
true(Default) All output values are forced to match the data type of the output columns.Mismatched values are written as null values.
false

All output values are written in their output form, regardless of the column's data type.

  • This behavior is the default for Cloud Dataprep by TRIFACTA INC. and Trifacta Wrangler.
Mismatched values are written as-is.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter accordingly:

    "webapp.enableTypecastOutput" : true,
  3. Save your changes and restart the platform.

Disable exporting job dependencies as flows

By default,  Trifacta Wrangler Enterprise  enables users to export the dependencies of a job that was executed as a flow. From the context menu in the Jobs tab in Flow View, select Export dependencies as Flow

  • The exported flow dependencies contains only the elements of the flow and its upstream dependencies that are required to execute the job.
  • This export can be re-imported into the environment as a separate flow to recapture the state of the flow at the time that the job was executed.

Notes:

  • Only the objects required to execute the job are included in the export. Unused datasets and recipes are not included. 
  • On import, the newly created flow points to the same source objects. If these have moved or have been deleted, the pointers need to be fixed.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to false:

    "feature.enableSnapshotExport" : true,
  3. Save your changes and restart the platform.

When disabled, verify that the Export dependencies as Flow option is not available from the context menu in the Jobs tab of Flow View. 

Enable Deletion of jobs

By default,  Trifacta Wrangler Enterprise does not permit the deletion of jobs. As needed, you can enable deletion of jobs. 

To enable this feature:

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to true:

    "feature.enableJobDeletion" : false,
  3. Save your changes and restart the platform.

When enabled, jobs can be deleted from Flow View page or from the Jobs page through the context menu. 

Disable parameterization

By default,  Trifacta Wrangler Enterprise supports the application of parameters to imported datasets. Datetime, wildcard, or variable parameters can be used to operationalize execution of jobs on different versions of the same dataset. For example, if a new dataset is dropped in the same folder each day with a different date value in the filename, you can apply parameters to the imported dataset to ensure that all matching datasets in the directory can be executed. For more information, see Overview of Parameterization.

To disable this feature, please complete the following steps.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to false:

    "feature.parameterization.enabled" : false,
  3. Save your changes and restart the platform.

Disable target schema matching

By default,  Trifacta Wrangler Enterprise enables you to create target schemas for each recipe in your dataset. These schemas are represented in the Transformer page as a panel above the column headers. For more information, see Overview of Target Matching.

If you prefer to disable this feature, please complete the following steps.

Tip: If there is no schema associated with a recipe, then the target schema matching features are not displayed.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to false:

    "feature.targetMatching.enabled" : false,
  3. Save your changes and restart the platform.

Enable uploading profile pictures

Optionally, you can configure the platform to all users to upload images to be used as their profile pictures. See User Profile Page.

Steps:


  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to true:

    "webapp.enableProfilePicture" : true,
  3. Save your changes and restart the platform.

Disable flow sharing

The flow sharing feature enables a user to share a flow with another user for collaboration. In this manner, a single source of truth can be retained as multiple users collaborate to transform the flow's datasets into the desired output. See Overview of Sharing.

 

Flow sharing is enabled by default. To disable flow sharing, please complete the following steps.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to false:

    "feature.flowSharing.enabled" : true,
  3. Save your changes and restart the platform.

Disable input swapping with datasets with parameters

By default, the Trifacta application enables swapping out a static dataset with a dataset with parameters. However, these changes can significantly affect overall data processing volumes. If needed, this feature can be disabled.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following parameter to false:

    "feature.parameterization.enableSwapWithDynamicDataset": true,
  3. Save your changes and restart the platform.

Disable column lineage recipe highlighting

By default, the Trifacta application can display lineage highlighting of applicable steps for a selected column. When enabled, you can select Show related steps from a column's drop-down menu, and all recipe steps that reference the column are highlighted in the recipe panel. 

Please complete the following steps to disable this feature.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the webapp.enableColumnLineageScriptHighlighting configuration flag to false:

    "webapp.enableColumnLineageScriptHighlighting": false,
  3. Save your changes and restart the platform.

Disable custom types

By default, you can create custom data types in Trifacta Wrangler Enterprise based off of a regular expression or an uploaded custom dictionaries of values. When a column is set to a custom data type, the values in the column are validated against the type specification. 

After a custom data type has been created, it cannot be removed from the platform.

To disable this feature, please complete the following steps.

Steps:

  1. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods.
  2. Set the following to false:

    "feature.enableCustomTypes": false,
  3. Save changes and restart the platform.

Other Configuration Topics


This page has no comments.