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

in order to implement custom pipeline functions in separate plugins the pipeline-plugin needs to be declared with shared class loader #81

Closed
kaililleby opened this Issue Aug 15, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@kaililleby

kaililleby commented Aug 15, 2016

Problem description

Adding new pipeline functions in separate plugins requires access to classes defined in the pipeline-plugin. With the release of graylog 2.1.x plugins by default do not share a global class loader (se #2508).

Steps to reproduce the problem

Create a plugin that registers a pipeline-function, deploy this with the latest 2.1 preview (server:2.1.0-beta.3-1).
The following exception will occur: java.lang.ClassNotFoundException: org.graylog.plugins.pipelineprocessor.ast.functions.AbstractFunction

I suppose adding a graylog-plugin.properties files containing the line isolated=false in both the the pipeline-plugin as well as the plugin implementing the custom pipeline-function would resolve the problem..

Environment

  • Graylog Version:2.1.0-beta.3-1
  • Pipeline Processor plugin version:1.1.0-beta.3.
  • Elasticsearch Version:
  • MongoDB Version:
  • Operating System: linux
  • Browser version:

@kroepke kroepke added the enhancement label Aug 18, 2016

@kroepke kroepke added this to the 1.1.0 milestone Aug 18, 2016

@kroepke

This comment has been minimized.

Member

kroepke commented Aug 18, 2016

We will enable this for the next release (beta.4 is already being built as I write this)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment