Skip to content
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

Data Prepper documentation updates: autogeneration campaign #7707

Merged

Conversation

dlvenable
Copy link
Member

Description

This is part of a campaign we have to move toward auto-generated documentation in Data Prepper.

This PR updates a few processors.

@chenqi0805

Issues Resolved

N/A

Version

N/A

Frontend features

N/A

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.

…port for autogeneration of processors by naming to match the processor and including the autogenerated comment.

Signed-off-by: David Venable <dlv@amazon.com>
@@ -15,11 +15,21 @@ The `parse_json` processor parses JSON data for an event, including any nested f

You can configure the `parse_json` processor with the following options.

<!--
This table is autogenerated. Do not edit it.
- name: obfuscate
Copy link
Contributor

Choose a reason for hiding this comment

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

Miscopy

<!--
This table is autogenerated. Do not edit it.
- name: obfuscate
- pluginType: parse_json
Copy link
Contributor

Choose a reason for hiding this comment

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

processor

Signed-off-by: David Venable <dlv@amazon.com>
@dlvenable
Copy link
Member Author

@chenqi0805 , Thanks for catching those errors. I pushed a new change.

…_type.md

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
…_type.md

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
…_type.md

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
…_type.md

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
…_type.md

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
| `keys`| Yes | Keys whose value needs to be converted to a different type. |
| `type` | No | Target type for the key-value pair. Possible values are `integer`, `long`, `double`, `big_decimal`, `string`, and `boolean`. Default value is `integer`. |
| `null_values` | No | String representation of what constitutes a `null` value. If the field value equals one of these strings, then the value is considered `null` and is converted to `null`. |
| `scale` | No | Modifies the scale when used to convert to a `big_decimal`. The default value is `0`. |
Copy link
Collaborator

@vagimeli vagimeli Jul 16, 2024

Choose a reason for hiding this comment

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

@dlvenable @chenqi0805 Is this saying that scale is only modified when the option is converted to big_decimal?

Copy link
Member Author

Choose a reason for hiding this comment

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

I just pushed a new commit that attempts to correct the wording.

We are modifying the scale of the big_decimal value itself. This field is only applicable for big_decimal.

Signed-off-by: David Venable <dlv@amazon.com>
Copy link
Collaborator

@vagimeli vagimeli left a comment

Choose a reason for hiding this comment

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

LGTM

@vagimeli
Copy link
Collaborator

vagimeli commented Jul 17, 2024

@hdhalter This PR is blocking from me merging it b/c build is failing (see image below). The link isn't broken (the hyperlink is correct https://opensearch.org/docs/latest/data-prepper/pipelines/configuration/processors/parse-json/). A similar error for another doc link is happening in #7708 . Can I bypass the build requirement so that I can merge?
Screenshot 2024-07-17 at 11 29 32 AM

@dlvenable dlvenable merged commit 27c4122 into opensearch-project:main Jul 19, 2024
5 checks passed
@dlvenable
Copy link
Member Author

@hdhalter This PR is blocking from me merging it b/c build is failing (see image below). The link isn't broken (the hyperlink is correct https://opensearch.org/docs/latest/data-prepper/pipelines/configuration/processors/parse-json/). A similar error for another doc link is happening in #7708 . Can I bypass the build requirement so that I can merge? Screenshot 2024-07-17 at 11 29 32 AM

Merging from main has fixed this.

opensearch-trigger-bot bot pushed a commit that referenced this pull request Jul 19, 2024
Updates Data Prepper documentation with some missing fields. Adds support for autogeneration of processors by naming to match the processor and including the autogenerated comment.

Signed-off-by: David Venable <dlv@amazon.com>

Signed-off-by: David Venable <dlv@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM>
(cherry picked from commit 27c4122)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@hdhalter
Copy link
Contributor

@dlvenable - there was a broken link. It was parse-json.md in the file and I just fixed it to be parse_json.md.

@hdhalter
Copy link
Contributor

Thanks for merging! I added the backport label.

@dlvenable dlvenable mentioned this pull request Jul 19, 2024
1 task
@dlvenable dlvenable deleted the data-prepper-autogenerate-campaign-1 branch July 19, 2024 18:55
leanneeliatra pushed a commit to leanneeliatra/opensearch-documentation-website-forl that referenced this pull request Jul 24, 2024
…ch-project#7707)

Updates Data Prepper documentation with some missing fields. Adds support for autogeneration of processors by naming to match the processor and including the autogenerated comment.

Signed-off-by: David Venable <dlv@amazon.com>

Signed-off-by: David Venable <dlv@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM>
Signed-off-by: leanne.laceybyrne@eliatra.com <leanne.laceybyrne@eliatra.com>
sandervandegeijn pushed a commit to sandervandegeijn/documentation-website that referenced this pull request Jul 30, 2024
…ch-project#7707)

Updates Data Prepper documentation with some missing fields. Adds support for autogeneration of processors by naming to match the processor and including the autogenerated comment.

Signed-off-by: David Venable <dlv@amazon.com>

Signed-off-by: David Venable <dlv@amazon.com>
Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Melissa Vagi <vagimeli@amazon.com>
Co-authored-by: Heather Halter <HDHALTER@AMAZON.COM>
Signed-off-by: Sander van de Geijn <sandervandegeijn@icloud.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants