Reads one or more CSV files as structured records following the format described in RFC 4180.
This input offers more control over CSV parsing than the
When parsing with a header row each line of the file will be consumed as a structured object, where the key names are determined from the header now. For example, the following CSV file:
Would produce the following messages:
If, however, the field
parse_header_row is set to
false then arrays are produced instead, like follows:
A list of file paths to read from. Each file will be read sequentially until the list is exhausted, at which point the input will close. Glob patterns are supported.
Whether to reference the first row as a header row. If set to true the output structure for messages will be an object where field keys are determined by the header row.
The delimiter to use for splitting values in each record, must be a single character.
Optionally process records in batches. This can help to speed up the consumption of exceptionally large CSV files. When the end of the file is reached the remaining records are processed as a (potentially smaller) batch.
This input is particularly useful when consuming CSV from files too large to
parse entirely within memory. However, in cases where CSV is consumed from other
input types it's also possible to parse them using the