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


For more information, see Configure Application Limits.

Configure File Format Support

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.


  1. To enable the feature, verify that the following parameter has been set to true:

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

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

  4. 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:


      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.

  5. Save your changes.

Supported Filename Extensions

You cannot upload a file with an unsupported or unlisted file extension. As needed, you can add extensions to the list of supported file formats, which enables the file to be uploaded. 

NOTE: Even if the file extension is added to this list, the platform may not be able to process the file. For more information, see Supported File Formats.

NOTE: The 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.


  1. Locate the following parameter and add file extensions. In the example, two new extensions have been added to the list:

    "webapp.client.allowedFileExtensions": [".log",".LOG"],

    Tip: To allow the uploading of files that do not have a file extension, enter a value of "" (empty string) in the array. Files without extensions are treated as TXT files by the .

  2. Save your changes and restart the platform.

Infer compression scheme

For imported files, the  infers compression based on the filename extension. For example, all files that have the .gz extension at the end of the filename are decompressed as GZIP files. This is the default behavior.

As needed, the  can be configured to infer any compression that has been applied to the file based on reading in the few bytes of the file. Based on that data signature, the file is passed to the appropriate internal service for decompression. 

Tip: This method is preferred if it's possible for filename extension to be improperly specified for the compression scheme.


  1. Locate the following parameter and set it to true:

    "eature.inferCompressionFromFileSignature.enabled": false,
  2. Save your changes and restart the platform.

Enabling Features

For more information on the feature flags to enable or disable features, see Configure Features.

Other Configuration Topics