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

remove ruby execution #11236

Comments

@jsvd
Copy link
Member

jsvd commented Oct 17, 2019

With java execution we no longer need the ruby one. There are know issues blocking this removal:

The Java Execution Engine has been the default engine since Logstash 7.0, and is capable of using plugins written in either Ruby or Java; removing the Ruby Execution Engine will not affect our ability to run existing pipelines, but will greatly reduce the surface area of all features and fixes within the engine(s), since we will no longer need to target two engines simultaneously.

@jsvd jsvd reopened this Dec 14, 2020
kaisecheng added a commit that referenced this issue Dec 14, 2020
* remove Logstash::Pipeline
* remove Engine.Ruby
* rewrite test cases which depend on ruby pipeline
Fixed: #11236
kaisecheng added a commit that referenced this issue Dec 14, 2020
kaisecheng added a commit that referenced this issue Dec 14, 2020
* remove config pipeline.java_execution
* remove ruby engine doc
Fixed: #11236
kaisecheng added a commit that referenced this issue Dec 15, 2020
* remove Logstash::Pipeline
* remove logstash/event, Logstash::SignalEvent
* remove Engine.Ruby on java side
* remove config pipeline.java_execution
Fixed: #11236
kaisecheng added a commit to kaisecheng/logstash that referenced this issue Dec 21, 2020
yaauie added a commit to yaauie/logstash that referenced this issue May 20, 2021
yaauie pushed a commit to yaauie/logstash that referenced this issue Jan 25, 2022
yaauie added a commit that referenced this issue Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment