From 7d10fc97f32c053f9336d1d69d530f39ef258268 Mon Sep 17 00:00:00 2001 From: Jesse Szwedko Date: Fri, 23 Jun 2023 14:54:20 -0700 Subject: [PATCH] chore(docs): Clarify `bytes` framing for streams (#17745) I'm not aware of any sources that separate "steam segments" so I updated the language a bit to account for how the `tcp` mode of the `socket` source handles `bytes` framing. Reference: https://github.com/vectordotdev/vector/issues/17136 Signed-off-by: Jesse Szwedko Signed-off-by: Jesse Szwedko --- website/cue/reference/components/sources.cue | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/cue/reference/components/sources.cue b/website/cue/reference/components/sources.cue index 9e3682067ee26..87053f76a4d3d 100644 --- a/website/cue/reference/components/sources.cue +++ b/website/cue/reference/components/sources.cue @@ -94,7 +94,7 @@ components: sources: [Name=string]: { type: string: { default: features.codecs.default_framing enum: { - bytes: "Byte frames are passed through as-is according to the underlying I/O boundaries (e.g. split between messages or stream segments)." + bytes: "Byte frames are passed through as-is according to the underlying I/O boundaries (e.g. split between messages, payloads, or streams)." character_delimited: "Byte frames which are delimited by a chosen character." length_delimited: "Byte frames which are prefixed by an unsigned big-endian 32-bit integer indicating the length." newline_delimited: "Byte frames which are delimited by a newline character."