D toc

Excerpt
This section contains information on the fie formats and compression schemes that are supported for input to and output of the D s platform r true .

Info
NOTE: To work with formats that are proprietary to a desktop application, such as Microsoft Excel, you do not need the supporting application installed on your desktop.

Filenames

Info
NOTE: During import, the D s webapp type portal identifies file formats based on the extension of the filename. If no extension is provided, the D s webapp type portal  assumes that the submitted file is a text file of some kind. Non-text file formats, such as Avro and Parquet, require filename extensions.

Info
NOTE: Filenames that include special characters can cause problems during import or when publishing to a file-based datastore.

File path length limits

Maximum character limits for file paths:

• File paths to sources for imported datasets: 1024 

  Tip
  Tip: This limit (storagelocations) applies to both files and tables.

• File paths to output files:  2048 

  Tip
  Tip: This limit (writesettings) applies to files stored on any file-based storage location.

Forbidden characters in import filenames

The following list of characters present issues in the listed area of the product. If you encounter issues, the following listings may provide some guidance on where the issue occurred.

Tip
Tip: You should avoid using any of these characters in your import filenames. This list may not be complete for all available running environments.

• General:

  Code Block
  "/"

• Seb browser: 

  Code Block
  "\"

• Excel filenames:

  Code Block
  "#","{","}"

• Spark-based running environment:

  Code Block
  "{", "*", "\"

Native Input File Formats

The

D s platform

 can read and import directly these file formats:

• CSV

• JSON v1, including nested

  Info
  NOTE: JSON files can be read natively but often require additional work to properly structure into tabular format. Depending on how the D s webapp type portal  is configured (v1 or v2), JSON files may require conversion before they are available for use in the application. See "Converted file formats" below.

  
  

  Info
  NOTE: The D s platform  requires that JSON files be submitted with one valid JSON object per line. Consistently malformed JSON objects or objects that overlap linebreaks might cause import to fail.

• Plain Text
• LOG
• TSV

• Parquet

  Info
  NOTE: When working with datasets sourced from Parquet files, lineage information and the $sourcerownumber reference are not supported.

• Avro

  Info
  NOTE: When working with datasets sourced from Avro files, lineage information and the $sourcerownumber reference are not supported.

• Google Sheets
  
  

  D s ed
  r true editions gdpent,gdppro,gdpsta,gdppr,gdpst,awsent,awspro,awspr

  Info
  NOTE: Individual users must enable access to their Google Drive. No data other than Google Sheets is read from Google Drive.

Converted file formats

Files of the following type are not read into the product in their native format. Instead, these file types are converted using the Conversion Service into a file format that is natively supported, stored in the base storage layer, and then ingested for use in the product.

Info
NOTE: Compressed files that require conversion of the underlying file format are not supported for use in the product.

Converted file formats:

• Excel (XLS/XLSX)

  Info
  NOTE: Other Excel-related formats, such as XLSM format, are not supported. If you are encountering issues, try to Save As to XLS or XLSX from within the Microsoft Excel application.

  
  

  Tip
  Tip: You may import multiple worksheets from a single workbook at one time.

• Google Sheets

  D s ed
  r true editions gdpent,gdppro,gdpsta,gdppr,gdpst,awsent,awspro,awspr

  Tip
  Tip: You may import multiple sheets from a single Google Sheet at one time.

• PDF

• JSON

Notes on JSON:

There are two methods of ingesting JSON files for use in the product. 

• JSON v2 - This newer version reads the JSON source file through the Conversion Service, which stores a restructured version of the data in tabular format on the base storage layer for quick and simple use within the application. 

  Tip
  Tip: This method is enabled by default and is recommended. For more information, see Working with JSON v2.

• JSON v1 - This older version reads JSON files directly into the platform as text files. However, this method often requires additional work to restructure the data into tabular format. For more information, see Working with JSON v1.

Parsing Limits

After a file is passed into the 

D s webapp

,  a set of transformations is applied to it to prepare it for use in the application. These transformations may impose additional limits on the file that is imported. When these transformations fail, the file may be imported into the application as a single column of data. For more information, see Initial Parsing Steps. 

Native Output File Formats

D s product

 can write to these file formats:

Info
NOTE: Some output formats may need to be enabled by an administrator.

• CSV
• JSON

• Hyper

  Info
  NOTE: Publication of results in Hyper format may require additional configuration. See below.

• Avro

  Info
  NOTE: The D s photon and Spark running environments apply Snappy compression to this format.

• Parquet

  Info
  NOTE: The D s photon and Spark running environments apply Snappy compression to this format.

Compression Algorithms

When a file is imported, the 

D s webapp

 attempts to infer the compression algorithm in use based on the filename extension. For example, .gz files are assumed to be compressed with GZIP. 

Info
NOTE: Import of a compressed file whose underlying format requires conversion through the Conversion Service is not supported.

Read Native File Formats

Write Native File Formats

Snappy compression formats

D s product

supports the following variants of Snappy compression format:

D s also
inCQL true label ((label = "file") OR (label = "file"))