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

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

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


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

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: You should avoid using any of these characters in your import filenames. This list may not be complete for all available running environments.

Native Input File Formats

 can read and import directly these file formats:

For more information on data is handled initially, see Initial Parsing Steps in the User Guide.

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.

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

Converted file formats:


Notes on JSON:

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

Native Output File Formats

 can write to these file formats:

Compression Algorithms

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

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

Snappy compression formats

supports the following variants of Snappy compression format:

File extension

Format name

Notes

.sz

Framing2 format

See: https://github.com/google/snappy/blob/master/framing_format.txt 

.snappy

Hadoop-snappy format

See: https://code.google.com/p/hadoop-snappy/

NOTE: Xerial's snappy-java format, which is also written with a .snappy file extension by default, is not supported.