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

doc: add REE removal to 8.0 breaking changes #12914

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

yaauie
Copy link
Member

@yaauie yaauie commented May 20, 2021

Release notes

[rn:skip]

What does this PR do?

Adds an entry to the breaking changes doc for the 8.0 removal of the Ruby Execution Engine, which was merged in #12490

Why is it important/What is the impact to the user?

Helps users considering upgrading to Logstash 8.0 understand the scope of changes.

Checklist

  • [ ] My code follows the style guidelines of this project
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files (and/or docker env variables)
  • [ ] I have added tests that prove my fix is effective or that my feature works

How to test this PR locally

Related issues

Related: #11236

The Execution Engine transforms pipeline definitions into executable code, and manages that code's execution.
Since {ls} 7.0, the Java Execution Engine (JEE) has been the default, but users could still configure their installation to use the legacy Ruby Execution Engine (REE).
The option to use REE is removed in 8.0.

Copy link
Contributor

Choose a reason for hiding this comment

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

@yaauie, looks like we added this issue in #13693:

[[bc-ruby-engine]]
===== Ruby Execution Engine removed
The Java Execution Engine has been the default engine since Logstash 7.0, and works with plugins written in either Ruby or Java.
Removal of the Ruby Execution Engine will not affect the ability to run existing pipelines. https://github.com/elastic/logstash/pull/12517[#12517]

Unless you want to tweak what's there, I think we can close this one.

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.

3 participants