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

Use correct ES analyzer in Messages#analyze() #2209

Merged
merged 1 commit into from May 10, 2016
Merged

Conversation

@joschi
Copy link
Contributor

@joschi joschi commented May 10, 2016

The Messages#analyze() method always used the "standard" analyzer of Elasticsearch, even if Graylog had been configured otherwise (elasticsearch_analyzer configuration setting).

This PR adds the correct option to the Elasticsearch Analyze request so that the configure analyzer is being used.

@joschi joschi added this to the 2.0.1 milestone May 10, 2016
@dennisoelkers dennisoelkers self-assigned this May 10, 2016
@dennisoelkers dennisoelkers merged commit 4877919 into 2.0 May 10, 2016
4 checks passed
4 checks passed
@garybot2
ci-server-integration Jenkins build graylog2-server-integration-pr 895 has succeeded
Details
@garybot2
ci-web-linter Jenkins build graylog-pr-linter-check 383 has succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@dennisoelkers dennisoelkers deleted the message-analyzer branch May 10, 2016
dennisoelkers added a commit that referenced this pull request May 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants