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

Plugin version 3.1.6 issue #65

Open
YakobovLior opened this issue Aug 19, 2019 · 5 comments
Open

Plugin version 3.1.6 issue #65

YakobovLior opened this issue Aug 19, 2019 · 5 comments

Comments

@YakobovLior
Copy link

Hello,
I have upgraded the plugin from 3.1.5 to 3.1.6 to have the support of SSL against the MongoDB,
but it looks like version 3.1.6 is accidentally missing the "isodate" option (when I add it to the configuration file it complains of invalid number of arguments, and removing it fixes the issue).
Are there plans to release new version soon which will solve this issue?
Thanks,
Lior

rmmorrison added a commit to rmmorrison/logstash-output-mongodb that referenced this issue Aug 23, 2019
rmmorrison added a commit to rmmorrison/logstash-output-mongodb that referenced this issue Aug 23, 2019
@rmmorrison
Copy link
Contributor

I've opened pull request #66 with a fix for this issue.

@singhksandeep25
Copy link

Hey @rmmorrison what else do I need to do in order to replicate your solution on 3.1.6 (locally)? After editing the respective functions in the files, do I need to compile the plugin or anything?

@rmmorrison
Copy link
Contributor

@singhksandeep25 yes, you'll need to compile using the instructions in the readme. Once you've got the gem built, it can be added to a Logstash installation using the logstash-plugin command, see instructions here: https://www.elastic.co/guide/en/logstash/current/working-with-plugins.html#installing-local-plugins

@singhksandeep25
Copy link

@rmmorrison Thanks a lot!! First I tried to use logstash-output-mongodb-3.1.5, but the mongo driver in that version is very old and it was causing troubles while connecting to mongodb atlas. So had to change the dependencies of mongo and bson in the logstash-output-mongodb.gemspec and in corporate your changes, the it worked.

@arichiardi
Copy link

arichiardi commented Oct 7, 2020

Additional data point on our side, reverting to 3.1.5 worked around the issue

arichiardi pushed a commit to elasticpath/logstash-output-mongodb that referenced this issue Oct 13, 2020
jsvd pushed a commit that referenced this issue Jan 31, 2022
…fixes #60, #64, #65) (#66)

Add missing second argument to to_bson methods, introduced with underlying Mongo driver update (fixes issues #60, #64, #65)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants