Cloud concept · Updated

Comma-Separated Values - Comma-Separated Values (CSV) is a plain-text format that represents tabular records as fields separated by commas.

In short

CSV provides a widely supported way to exchange flat datasets between applications, cloud storage, analytics engines, and machine learning pipelines. Its simplicity makes ingestion and export straightforward, but reliable processing requires explicit agreements about schema, quoting, missing values, and encoding.

Cloud Concepts Hub →

6 key aspects of Comma-Separated Values

CSV combines broad compatibility with a need for explicit schema, parsing, validation, and file-layout decisions.

01
Portable tabular interchange

CSV is widely supported by databases, data-processing libraries, spreadsheets, and ML tools. It works best for flat records with a consistent set of columns rather than nested objects or variable structures.

02
External schema contract

Define column order, data types, headers, encoding, and missing-value conventions outside the file. Preserve identifiers as strings when leading zeros or exact text values matter.

03
Explicit parsing rules

Use a CSV-aware parser that handles quoted delimiters, escaped quotes, and supported multiline fields. Test the producer and consumer together because CSV dialects and parser capabilities differ.

04
Access-pattern-driven selection

CSV suits interoperability and full-record sequential reads. Prefer Parquet or ORC for large, repeated queries that access only selected columns, and consider JSON for nested records.

05
ML input compatibility

Verify the training or inference consumer's requirements for headers, target-column position, content type, and missing values. Validate these requirements before writing the final dataset.

06
Compression and parallelism

Compression saves storage and transfer bandwidth but can limit parallel reading within a file. Balance file sizes, file counts, and partitioning to support the intended processing engine.

Cloud services for Comma-Separated Values

Amazon S3 can hold incoming CSV files and separate validated outputs. AWS Glue can inspect and transform those files, enforce a schema, and publish table metadata for Amazon Athena. Athena enables SQL-based exploration and quality checks, provided its CSV parser supports the source file's conventions. For recurring analytical workloads, Glue can write Parquet or ORC while preserving raw CSV for traceability. Amazon SageMaker AI can consume a compatible prepared dataset for training or inference, with the final export tailored to the selected algorithm or container rather than assuming every CSV layout is interchangeable.

Amazon S3Amazon S3

Stores raw CSV exports, validated datasets, and generated predictions as objects. S3 stores bytes rather than enforcing CSV schemas, so processing tools must validate records and interpret fields.

AWS GlueAWS Glue

Reads and writes CSV through ETL jobs and can catalog datasets for downstream consumers. Jobs can apply explicit schemas, normalize values, and convert CSV into partitioned Parquet or ORC for analytical access.

Amazon AthenaAmazon Athena

Queries CSV stored in S3 using table definitions and an appropriate serializer/deserializer, such as OpenCSVSerde for supported quoted CSV. Configure header handling and types carefully; OpenCSVSerde does not support embedded line breaks within fields.

Comma-Separated Values exam questions

Real practice exam questions on Comma-Separated Values, with the correct answer and its explanation. Answer them with every option in the exam simulator.

MLA-C02 (beta)

A machine learning engineer is building an AWS Glue ETL pipeline for daily event data in Amazon S3. Each event contains 240 fields. Repeated feature-engineering jobs typically read only 8 fields, so the curated dataset must support reading selected columns without reading the values of unrelated columns. The pipeline must also produce a separate training dataset for an existing container that accepts only uncompressed, headerless CSV files with the numeric target in the first column and numeric features in a fixed order. Which solution meets both requirements?

Show answerCORRECT ANSWER

Use a Glue job to write the curated dataset as compressed Parquet. Select and order the numeric target and feature columns, then write a separate CSV dataset with compression disabled and writeHeader set to false.

Parquet supports column projection, allowing compatible readers to read the required fields without reading unrelated column values. A separate CSV export with explicit column ordering, no header, and no compression satisfies the training container's input contract.

SAA-C03

An insurance company receives daily UTF-8 CSV exports in Amazon S3. Each file has a header row. Policy identifiers contain only digits but can begin with zeros that must be preserved. Customer address fields are enclosed in double quotes and can contain commas and embedded line breaks. The company needs a serverless batch transformation that creates a separate Apache Parquet dataset while preserving every identifier and keeping each address in a single field. Which solution meets these requirements?

Show answerCORRECT ANSWER

Run an AWS Glue Spark job with a CSV reader configured for headers, double-quote handling, and multiline records. Provide an explicit schema that reads policy identifiers as strings, and write the results as Parquet to a separate S3 prefix.

A CSV-aware reader preserves commas inside quoted fields, and multiline support preserves embedded line breaks within an address rather than treating them as new records. Reading identifiers as strings from the start preserves leading zeros. AWS Glue provides serverless batch processing and can write a separate Parquet dataset.

Practice Comma-Separated Values in a full exam

Questions on Comma-Separated Values in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Comma-Separated Values

3 min read

Comma-Separated Values, usually abbreviated CSV, represents a table as a sequence of records whose fields are separated by commas. A file can include a header record containing column names, but headers are optional. Records normally end with a line break, although quoted fields can themselves contain line breaks. CSV is useful for exchanging customer attributes, transaction records, training examples, and prediction results because many databases, spreadsheets, and programming libraries can read and write it.

CSV does not embed a typed schema. A value such as 00123 might represent an identifier rather than the number 123, and a date such as 03/04/2025 is ambiguous without an agreed convention. Production pipelines should define column names, field order, data types, date formats, character encoding, and missing-value rules separately. UTF-8 and unambiguous date formats are practical defaults when supported by the producers and consumers. Automated type inference is convenient for exploration, but it can misclassify identifiers or fail when later records contain unexpected values.

Correct parsing requires more than splitting each line at commas. A customer name such as "Smith, Jane" must remain one field. In a common CSV convention, fields containing commas, double quotes, or line breaks are enclosed in double quotes, and an embedded double quote is represented by two double quotes. Parser behavior varies, so producers and consumers must agree on these rules. An empty field, an empty quoted string, and a literal NULL do not have universally consistent meanings across tools.

In cloud pipelines, CSV files commonly arrive in object storage from operational systems or external partners. An ingestion job validates the field count and schema, separates malformed records, normalizes values, and writes a clean dataset. For example, a transaction export might contain transaction_id, event_time, amount, and fraud_label. The preparation job preserves transaction_id as text, parses event_time consistently, validates amount, and checks that fraud_label has an allowed value before creating training data.

Choose CSV when broad interoperability, simple exports, or sequential processing of flat records matters most. It can also suit machine learning training jobs that read most or all features in each example and explicitly support CSV input. Consumer requirements are critical: some training algorithms expect no header and require the target label in a particular column. A .csv extension alone does not guarantee compatibility, so confirm the algorithm's content type, column ordering, and missing-value requirements.

For repeated analytical queries over large datasets, Parquet or ORC is often more efficient. These columnar formats support typed columns, efficient compression, and metadata that query engines can use to avoid unnecessary reads. CSV generally requires parsing records even when a query needs only a few columns. JSON is often more appropriate for nested or irregular records, although its structure and repeated field names introduce different overheads. Format selection should follow access patterns rather than a blanket preference for text or binary storage.

Compression reduces CSV storage and transfer volume, but ordinary gzip files generally cannot be split internally for parallel processing by common distributed readers. Multiple appropriately sized files can improve concurrency, while excessive small files add scheduling and listing overhead. Partitioning object-storage paths by a useful attribute, such as event date, can reduce the files a query must inspect. CSV is therefore an effective interchange format, but it is not automatically the best long-term analytical format or a substitute for schema validation.

Learn Comma-Separated Values in lessons

3 short lessons on Comma-Separated Values in 2 certification courses.

Open the lessons