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

Documentation improvements for a number of Data Prepper processors. #5023

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

dlvenable
Copy link
Member

Description

Updates some enumerations used in processors to support the @JsonValue annotation. Corrects @JsonClassDescription to use HTML rather than Markdown. Various unit test improvements for modified unit tests.

This follows on other PRs such as:

In particular, for #4985, I missed the @JsonClassDescription headers.

Issues Resolved

None

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

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

Updates some enumerations used in processors to support the @JsonValue. Corrects @JsonClassDescription to use HTML rather than Markdown.

Signed-off-by: David Venable <[email protected]>
@JsonProperty("drop_when")
@NotEmpty
private String dropWhen;

@JsonPropertyDescription("Specifies how exceptions are handled when an exception occurs while evaluating an event. Default value is 'drop', which drops the event so that it is not sent to OpenSearch. Available options are 'drop', 'drop_silently', 'skip', and 'skip_silently'.")
@JsonPropertyDescription("Specifies how exceptions are handled when an exception occurs while evaluating an event. Default value is <code>drop</code>, which drops the event so that it is not sent to further processors or sinks.")
Copy link
Member

Choose a reason for hiding this comment

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

Looks like this one was incorrect before, as the default behavior is to SKIP

@JsonProperty(INCLUDE_PERFORMANCE_METADATA)
@JsonPropertyDescription("A <code>Boolean</code> on whether to include performance metadata into event metadata, " +
"e.g. _total_grok_patterns_attempted, _total_grok_processing_time.")
@JsonPropertyDescription("A boolean value to determine whether or not to performance metadata into event metadata. " +
Copy link
Member

Choose a reason for hiding this comment

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

looks like typo in whether or not to performance metadata

…s performance metadata tags.

Signed-off-by: David Venable <[email protected]>
@dlvenable dlvenable merged commit 27337ea into opensearch-project:main Oct 7, 2024
44 of 47 checks passed
@dlvenable dlvenable deleted the doc-improvements-2 branch October 9, 2024 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants