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

Unresolved functions not properly handled #25

Closed
kroepke opened this Issue May 4, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@kroepke
Member

kroepke commented May 4, 2016

Problem description

Using unresolved functions does not lead to proper error message.
Related to #24

Steps to reproduce the problem

  1. Create a rule like
rule "test"
when true
then
  let x = doesnotexist(pattern: "a");
end
  1. There is no error about the non-existing function
  2. There will be exceptions thrown during preprocessing function arguments, because the unresolved function placeholder does not have any functions.

Environment

  • Graylog Version: 2.0.0
  • Pipeline Processor plugin version: 1.0.0-beta.2
  • Elasticsearch Version: n/a
  • MongoDB Version: n/a
  • Operating System: n/a
  • Browser version: n/a

@kroepke kroepke self-assigned this May 4, 2016

@kroepke kroepke added the bug label May 4, 2016

@kroepke kroepke added this to the 1.0.0 milestone May 4, 2016

@kroepke kroepke modified the milestone: 1.0.0 Jul 29, 2016

@kroepke kroepke closed this in 06e64b7 Aug 3, 2016

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