Big Data File Formats Explained
Big Data File Formats Explained
Use the write file format for your next big data project.
Join the DZone community and get the full member experience.Join For Free
Apache Spark supports many different data formats, such as the ubiquitous CSV format and web-friendly JSON format. Common formats used primarily for big data analytical purposes are Apache Parquet and Apache Avro.
You may also like: Apache Spark.
CSV (comma-separated values) files are commonly used to exchange tabular data between systems using plain text. CSV is a row-based file format, which means that every line of the file is the row in the table. Basically, CSV contains a header row that provides column names for the data, otherwise, files are considered partially structured.
CSV files cannot initially present hierarchical or relational data. Data connections are typically organized by using multiple CSV files. Foreign keys are stored in columns of one or more files, but the links between these files are not expressed by the format itself. Also, CSV format is not fully standardized, so files can use delimiters other than commas, such as tabs or spaces.
One of the other properties of CSV files is that they are only splittable when it is a raw, uncompressed file or when a splittable compression format is used such as bzip2 or lzo (note: lzo needs to be indexed to be splittable!).
- CSV is human-readable and easy to edit manually.
- CSV provides a straightforward information schema.
- CSV is processed by almost all existing applications.
- CSV is simple to implement and parse.
- CSV is compact. For XML you start tag and end tag for each column in each row. In CSV you write the column headers only once.
- CSV allows working with flat data. Complex data structures need to be handled aside from format.
- No support for column types. There is no distinction between text and numeric columns.
- No standard way to represent binary data.
- Problems with importing CSV (no distinction between NULL and quotes).
- Poor support of special characters.
- Lack of universal standard.
Despite its limitations, CSV files are a popular choice for data sharing, as they are supported by a wide range of business applications, consumer, and scientific applications. Similarly, most batch and streaming data processing modules (for example, Spark and Hadoop) initially support serialization and deserialization of CSV files and offer ways to add a schema when reading.
Since a lot of data transferring is already using JSON format, most web languages initially support JSON or use external libraries to serialize and deserialize JSON data. Thanks to this support, JSON is used in logical formats by presenting data structures, interchange formats for hot data, and cold data stores.
Many batches and stream data processing modules natively support JSON serialization and deserialization. Although the data contained in JSON documents can ultimately be stored in more performance-optimized formats, such as Parquet or Avro — they serve raw data, which is very important for reprocessing data (if necessary).
JSON files have several advantages:
- JSON supports hierarchical structures, simplifying the storage of related data in one document and the presentation of complex relations.
- Most languages provide simplified JSON serialization libraries or built-in support for JSON serialization/deserialization.
- JSON supports lists of objects, helping to avoid erratic transformations of lists into a relational data model.
- JSON is a widely used file format for NoSQL databases such as MongoDB, Couchbase and Azure Cosmos DB.
- Built-in support in most nowadays tools.
Launched in 2013, Parquet was developed by Cloudera and Twitter to serve as a column-based storage format, optimized for work with multi-column datasets. Because data is stored by columns, it can be highly compressed (compression algorithms perform better on data with low information entropy, which is usually contained in columns) and splittable. The developers of the format claim that this storage format is ideal for Big Data problems.
Unlike CSV and JSON, Parquet files are binary files that contain metadata about their content. So, without reading/parsing the content of the file(s), Spark can just rely on the metadata to determine column names, compression/encodings, data types, and even some basic statistics. The column metadata for a Parquet file is stored at the end of the file, which allows for fast, one-pass writing.
Parquet is optimized for the Write Once Read Many (WORM) paradigm. It's slow to write, but incredibly fast to read, especially when you're only accessing a subset of the total columns. Parquet is a good choice for read-heavy workloads. For use cases requiring operating on entire rows of data, a format like CSV or AVRO should be used.
The advantages of data storage in Parquet:
- Parquet is a columnar format. Only required columns would be fetched/read, which reduces the disk I/O. This concept is called projection pushdown.
- Schema travels with the data, so data is self-describing.
- Despite the fact that it is created for HDFS, data can be stored in other file systems, such as GlusterFs or on top of NFS.
- Parquet are just files, which means that it is easy to work with them, move, back up and replicate.
- Native support in Spark out of the box provides the ability to simply take and save the file to your storage.
- Parquet provides very good compression up to 75% when used even with the compression formats like snappy.
- As practice shows, this format is the fastest for reading workflows compared to other file formats.
- Parquet is well suited for data warehouse kind of solutions where aggregations are required on certain columns over a huge set of data.
- Parquet can be read and written using Avro API and Avro Schema (which gives the idea to store all raw data in Avro format but all processed data in Parquet).
- It also provides predicate pushdown, thus reducing further disk I/O cost.
Predicate Pushdown/Filter Pushdown
The basic idea of predicate pushdown is that certain parts of queries (the predicates) can be "pushed" to where data is stored. For example, when we give some filter criteria, the data store tries to filter records at the time of reading from disk.
The advantage of predicate pushdown is fewer disks I/O will happen. As a result, performance is better. Otherwise, whole data would be brought into memory and then filtered, which results in large memory requirements.
This optimization can drastically reduce query/processing time by filtering out data earlier, rather than later. Depending on the processing framework, predicate pushdown can optimize your query by doing things like filtering data before it is transferred over the network, filtering data before loading into memory, or skipping reading entire files or chunks of files.
This concept is followed by most RDBMS and has been followed by big data storage formats like Parquet and ORC as well.
When data is read from the data store, only those columns would be read which are required, as per the query; not all the fields would be read. Generally, columnar formats like Parquets and ORC follow this concept, which results in better I/O performance.
Apache Avro was released by the Hadoop working group in 2009. It is a row-based format that is highly splittable. It is also described as a data serialization system similar to Java Serialization. The schema is stored in JSON format, while the data is stored in binary format, minimizing file size and maximizing efficiency.
Avro has robust support for schema evolution by managing added fields, missing fields, and fields that have changed. This allows old software to read the new data and new software to read the old data — a critical feature if your data has the potential to change.
With Avro’s capacity to manage schema evolution, it’s possible to update components independently at different times with a low risk of incompatibility. This saves applications from having to write if-else statements to process different schema versions and saves the developer from having to look at old code to understand old schemas.
Because all versions of the schema are stored in a human-readable JSON header, it’s easy to understand all available fields.
Avro can support many different programming languages. Because the schema is stored in JSON while the data is in binary, Avro is a relatively compact option for both persistent data storage and wire transfer. Avro is typically the format of choice for write-heavy workloads, given its easy to append new rows.
- Avro is language-neutral data serialization.
- Avro stores the schema in the header of the file so data is self-describing.
- Avro formatted files are splittable and compressible, so it's a good candidate for data storage in the Hadoop ecosystem.
- The schema used to read an Avro file need not be the same as schema which was used to write the files. This makes it possible to add new fields independently.
- Just as with Sequence Files, Avro files also contain Sync markers to separate the blocks. This makes it highly splittable.
- These blocks can be compressed using compression formats such as snappy.
*JSON has the same problems with splittability when compressed as CSVs, with one extra difference. When the “wholeFile” option is set to true (re: SPARK-18352), JSON is NOT splittable.
- CSV should generally be the fastest to write. JSON should be the easiest for a human to understand. Parquet should be the fastest to read a subset of the columns, while Avro should be the fastest to read all columns at once.
- JSON is the standard for communicating on the web. APIs and websites are constantly communicating using JSON because of their usability properties such as well-defined schemas.
- Parquet and Avro are definitely more optimized for Big Data needs — splittability, compression support, great support for complex data structures. Unfortunately, readability and writing speed are quite bad.
Thank you for reading!
Any questions? Leave your comment below to start fantastic discussions!
Opinions expressed by DZone contributors are their own.