-
Notifications
You must be signed in to change notification settings - Fork 626
expanding on join data prepper docs #11502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
expanding on join data prepper docs #11502
Conversation
Signed-off-by: Anton Rubin <[email protected]>
|
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. |
|
@dlvenable could you please review this PR |
dlvenable
left a comment
There was a problem hiding this 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.
_data-prepper/pipelines/join.md
Outdated
| ## 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 `","`. |
There was a problem hiding this comment.
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?
_data-prepper/pipelines/join.md
Outdated
| - **string**: All elements concatenated with the chosen delimiter. | ||
|
|
||
| ## Quick examples | ||
| - `join("-", /tags)` returns `"prod-api-us"` for `tags: ["prod","api","us"]` |
There was a problem hiding this comment.
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.
_data-prepper/pipelines/join.md
Outdated
| ## 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`: |
There was a problem hiding this comment.
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]>
|
@dlvenable thats updated now |
Description
expanding on join data prepper docs
Version
all
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.