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.

Sign up for GitHub

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

Jump to bottom

[8.1](backport #30668) libbeat: Don't force an ignore_above limit on wildcard fields #30708

Merged
merged 1 commit into from
Mar 7, 2022
Merged

[8.1](backport #30668) libbeat: Don't force an ignore_above limit on wildcard fields #30708

merged 1 commit into from
Mar 7, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 7, 2022 •
edited by zube bot
Loading

This is an automatic backport of pull request #30668 done by Mergify.

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@adriansr
libbeat: Don't force an ignore_above limit on wildcard fields (#30668)
dd88c70 
Modifies libbeat's template processor to stop hardcoding a default
`ignore_above` limit of 1024 on wildcard fields. This behavior was
inherited from keyword fields.

Closes #30096

(cherry picked from commit 677229f)
@mergify mergify bot added the backport label Mar 7, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 7, 2022
@botelastic
Copy link

botelastic bot commented Mar 7, 2022

This pull request doesn't have a Team:<team> label.

@mergify
Copy link
Contributor Author

mergify bot commented Mar 7, 2022

This pull request has not been merged yet. Could you please review and merge it @adriansr? 🙏

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview [preview](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-03-07T08:11:50.897Z&rangeTo=2022-03-07T08:31:50.897Z&transactionName=BUILD Beats/beats/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=4419aba059015aec3dfcd50f5caeb7fc&transactionId=6d9c7e05fe809908)

Expand to view the summary

Build stats

  • Start Time: 2022-03-07T08:21:50.897+0000

  • Duration: 107 min 12 sec

Test stats 🧪

Test Results
Failed 0
Passed 42934
Skipped 3854
Total 46788

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@adriansr adriansr merged commit 1387fd3 into 8.1 Mar 7, 2022
@mergify mergify bot deleted the mergify/bp/8.1/pr-30668 branch March 7, 2022 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@adriansr adriansr

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @adriansr