Re: driver, I do have a strong opinion. The zookzook driver is actively maintained, and it is up-to-date on the latest features such as transactions. Maintenance momentum is few and far between on Elixir libs, so we should jump on the bandwagon ASAP rather than investing our time building-up a competing lib.
johnnyshields
peoj
Fair enough! Maybe a good first investigation would be to swap out the driver and see if one can make the tests pass.
I imagine there is a nice way of allowing a user to decide which driver they want to use too.
0
scottmessinger
Over the new few weeks, I’m going to be working full time on upgrading the Mongo Ecto Library to be compatible with Ecto 3. Before I jump in, I wanted to check to see if anyone else has done all or part of this in another fork. I’d love to build upon existing work if at all possible!
8
peoj
I haven’t done any work but since posting on this thread earlier I’ve been working with GitHub - zookzook/elixir-mongodb-driver: MongoDB driver for Elixir · GitHub and it’s been working very nicely. I’m not sure if there have been any developments in the existing mongo driver included with the MongoDB Ecto lib but assuming not, I still believe it would be worth investigating integrating zookzook’s Mongo driver.
Glad you’re taking it on!
1
scottmessinger
I’d love to get @zookzook 's driver working with the adapter! The current problem is I’m running into this:
https://github.com/zookzook/elixir-mongodb-driver/issues/92
I have no idea why I’m getting that error. If I can get it spun up, I’d love to see how hard it would be to switch over or provide as an option.
0
scottmessinger
Also, update: my fork now works with Ecto 3. If anyone would like to try it out, please do. I’d love the feedback!
11
peoj
@hauleth @deadtrickster are you still planning to maintain the mongodb_ecto packages? @scottmessinger has put in some effort and it’d be great to get this wrapped into the officially maintained packages.
Please let us know so the community can pitch in!
1
mattei
peoj
I have been trying to elicit a response from the current maintainers of the mongodb and mongodb_ecto packages. I’ve not heard anything yet (if you’re reading, please just let us know what the plan is so we can plan accordingly).
As far as I can tell, those who would wish to use MongoDB + Ecto have:
- In terms of drivers,
mongodbandmongodb_driver. As has been pointed out, the latter has better support for newer MongoDB features. - In terms of Ecto, we have
mongodb_ectowhich hasn’t received any updates in some time, and the work of Scott and others in the form of a fork.
@scottmessinger’s efforts bring MongoDB + Ecto into a usable state, which is very welcome. I hope Scott you won’t mind me saying though that these are “just the beginning” of a few changes that are needed. There are also features in newer versions of MongoDB that would be nice to support too. In other words, the libraries are in need of TLC, it seems like there are people that are willing to put in the work, but we’re stuck here. My question is for everyone, what should we do to keep things moving forward?
Our current options seem quite undesirable for the community and the current maintainers:
- Another fork
- A separately published and maintained package
- Something else?
I really don’t wish to appear to be being negative or critical of anyone’s efforts here: We have a requirement in our company to use MongoDB in our stack, and it’d be great if we could take advantage of an Ecto + MongoDB integration along the way. That and I believe the community could really use a decent offering in this area. Those are my reasons for continuing to push :).
Edit:
I should also add that it seems that mongodb_driver came about in the first place because of a lack of maintenance from the mongodb driver original from which it draws. I’m all for competition but it’s worth pointing out that the same problem exists there too.
3
scottmessinger
@josevalim Several of us have been trying to get a hold of anyone at Kobil Systems (such as @hauleth and @deadtrickster ) to get the ownership of the mongodb_ecto library transferred over and we have totally failed to reach them. Could you help us out? We’d love to move the adapter (and driver) forward without making a fork and having two competing adapters in the small elixir mongodb ecosystem. Any ideas you have to help resolve this?
Thanks!
2