Skip to content

Conversation

@AntonEliatra
Copy link
Contributor

Description

expanding on join data prepper docs

Version

all

Checklist

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
    For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

@AntonEliatra
Copy link
Contributor Author

@dlvenable could you please review this PR

@kolchfa-aws kolchfa-aws added Tech review PR: Tech review in progress backport 3.3 labels Nov 6, 2025
Copy link
Member

@dlvenable dlvenable left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AntonEliatra , overall this looks good. I have a few small comments.

## Parameters

You can specify an alternative delimiter inside the expression. For example, `join("-", /source)` joins each source field using a hyphen `-` as the delimiter.
- **delimiter** (string, optional): The text placed between elements. Examples: `","`, `" | "`, `"; "`. Default is `","`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should use "string" instead of "text" as this is what we call these types. Thoughts?

- **string**: All elements concatenated with the chosen delimiter.

## Quick examples
- `join("-", /tags)` returns `"prod-api-us"` for `tags: ["prod","api","us"]`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should avoid using tags as an example. Tags is a different concept and this could cause confusion. Perhaps change change to labels. Also, see line 35 and update that example as well.

## Example
The following pipeline ingests JSON events using the HTTP source, uses `add_entries` with `join()` to build two new fields, `tags_csv` and `authors_pipe`:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, let's not use "tags" as the example. Maybe "labels" or something more specific.

Signed-off-by: Anton Rubin <[email protected]>
@AntonEliatra
Copy link
Contributor Author

@dlvenable thats updated now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 3.3 Tech review PR: Tech review in progress

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants