From cb86940b9e5c1d762fc0be25c533ff5d51ecd09d Mon Sep 17 00:00:00 2001 From: JakeSCahill Date: Wed, 22 Jul 2026 14:54:03 +0100 Subject: [PATCH] fix(csv): promote "Output CSV column order" out of the Metadata section The csv input's description nested "=== Output CSV column order" (a how-to for producing deterministic CSV output, with a Bloblang example) as a level-3 subsection under "== Metadata". It is not metadata, and tooling that extracts the Metadata section verbatim (the Redpanda Connect docs metadata partials) swept the whole subsection into the generated metadata reference. Promote it to a sibling "==" section so it stands on its own and no longer leaks into the metadata block. --- internal/impl/io/input_csv.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/impl/io/input_csv.go b/internal/impl/io/input_csv.go index 056b658e2..f3e53240c 100644 --- a/internal/impl/io/input_csv.go +++ b/internal/impl/io/input_csv.go @@ -70,7 +70,7 @@ You can access these metadata fields using xref:configuration:interpolation.adoc Note: The `+"`header`"+` field is only set when `+"`parse_header_row`"+` is `+"`true`"+`. -=== Output CSV column order +== Output CSV column order When xref:guides:bloblang/advanced.adoc#creating-csv[creating CSV] from Redpanda Connect messages, the columns must be sorted lexicographically to make the output deterministic. Alternatively, when using the `+"`csv`"+` input, one can leverage the `+"`header`"+` metadata field to retrieve the column order: