Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version next

...

Excerpt

This section contains information on the fie formats and compression schemes that are supported for input to and output of of the

d-s-productplatform
rtrue

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.

...

Info

NOTE: During import, the

D s webapp
typeportal
identifies file formats based on the extension of the filename. If no extension is provided, the
D s webapp
type
assumes
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.

...

  • General:

    Code Block
    "/"
  • Seb browser: 

    Code Block
    "\"
  • Excel filenames:

    Code Block
    "#","{","}"
  • Spark-based running environment:

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

  • D s dataflow
    running environment:

    Code Block
    @

Native Input File Formats

The

d-s-productplatform
rtrue
 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
    typeportal
    is  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-productplatform
    requires  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.

...

  • 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. See Import Excel Data in the User Guide.

  • Google Sheets

    D s ed
    rtrue
    editionsgdpent,gdppro,gdpsta,gdppr,gdpst,awsent,awspro,awspr

    Tip

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

  • PDF

  • JSON v2

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

  • Avro

    Info

    NOTE: The

    D s photon
    and Spark running environments apply Snappy compression to this format.

  • BigQuery Table

Compression Algorithms

...

Info

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


Read Native File Formats



 GZIPBZIPSnappyNotes
CSV SupportedSupportedSupported
JSON v2Not supportedNot supportedNot supportedA converted file format. See above.
JSON v1SupportedSupportedSupportedNot a converted file format. See above.
Avro  

Supported

...

Write Native File Formats

...



GZIPBZIPSnappy
CSVSupportedSupportedNot supported
JSONSupportedSupportedNot supported

...