-
Notifications
You must be signed in to change notification settings - Fork 62
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
MongoConverter support in Spring Modules #87
Comments
As workaround, i used aggregation and bson.Document, so i didn't need converters. |
thanks, we'll update you on this. |
Hi, we are quite busy right now. is this fix quite important for you or can wait? |
Sure, i can wait, we are in pre-prod stage right now. |
Any updates here? |
Hi @savvadem , I haven't able to look at this. As you had a workaround we have prioritise other things, like bugs, etc. Version 3 has been a major change internally, that's the reason we're still in BETA. I cannot tell you this will be fixed this week, but I will try to have a look to at least understand what we are talking about. Thanks |
I am having the same issue after upgrading to the non-BETA version 3.2.3 from 2.0.2. I am using Running with Spring Boot v2.1.11.RELEASE, Spring v5.1.12.RELEASE. Exception: Caused by: com.github.cloudyrock.mongock.MongockException: Can't find a codec for class java.time.ZonedDateTime. |
Sorry , I didn't update on this. I wasn't able to reproduce this, and we was distracted by some other more urgent matters. We'll look at this today. However, it would be nice if you can provide an example app that I can checkout out and reproduce easily. Thanks @Ovaro |
Hi @dieppa - this is on a Jhipster based app where I have moved to monogock rather than mongobee.
} And the example of a class that doesn't work: @document(collection = "job")
.... This all worked in version 2.0.2 but has stopped in version 3 and above. Mongock is being created in exactly the same way so have the converters registered (those debug log lines stating the converter is registered occurs way before the errors). |
Hello, that's probably because we migrate from a proxy approach to control the lock to implement decorators. Anyway, we have been able to reproduce it and doesn't seem that will be hard to fix. It will be fixed by Thursday evening. Cheers |
@dieppa Awesome! Great to hear it wasn't a big problem. I didn't look into the cause as I saw this open issue. Really appreciated. Cheers. |
@Ovaro, I believe that if you use MongoTemplate, instead of MongoClient, it works fine. Can you check, please? Just notice that currently there is a bug using MongoTemplate, which affects for example to fields with annotated with @indexed. However this is fixed, but not released yet. Will be released before Thursday, together with any fix this issue require, if it's the case. |
@dieppa Yeah, I assumed that earlier as I used to pass in the MongoTemplate to mongock before the 3.2.3 upgrade. I tried use the MongoTemplate based constructor and ran into the index issue you describe. The funny thing is that when I reverted to 2.0.2 I left the mongo template out and it works without passing in the MongoTemplate. But yes, I do agree that might be the problem for Mongock and am happy to wait for the Index fix. Cheers |
great, will keep you updated ;) |
FYI- Jhipster made a decision to stay with mongobee, but it doesn't support Mongo Atlas, hence why I switched (there is an issue on their github issue list if you want to see their reasoning on staying with Mongobee. You might want to convince them to switch to monogock - you would immediately get thousands of users. Just a thought. |
Thanks @Ovaro. Mongobee not only doesn't support Atlas, they don't provide a decent lock mechanism neither a lot of other important features Mongock gives you. But more important than that, they stopped maintaining the library. Actually Mongock started because of a PR that they never reviewed. Since then, we have added a lot of more functionalities and much more we have in our roadmap, which will be published in the next weeks together with our plan to take Mongock to the next level. But we already know their reasons to not move to Mongock. They are afraidthat we might stop the maintaining Mongock too. However when they decided that, more than a year ago, Mongock had just 11 stars(one of their reasons) now it has 93. I know it's still not much, but I haven't pushed it yet and we not only have continued maintaining the project, we got ambitious plans for it. Thanks a lot! |
Hello @Ovaro , I said that we were able to release a version today, but I need to say sorry because that won't be possible. I think I will be able to have it done by tomorrow, but then we need to perform some tests, so it will be probably Monday. Regards |
@dieppa No worries! I have rolled back to 2.0.2 so this bug hasn't slowed me down. Cheers |
Hey @Ovaro , version 3.2.4 is released and should work for you. Please let me know. |
@dieppa Just tested with the new MongoTemplate constructor and works perfectly. Thanks!! |
Thank you. I close this :) |
Hi,
I have some problems with mongock.
It seems that MongoTemplateDecoratorImpl doesn't catch
and in the end i receive this exception:
dependency version:
compile 'com.github.cloudyrock.mongock:mongock-spring:3.0.2.BETA'
Spring Boot 2.0.5.RELEASE
The text was updated successfully, but these errors were encountered: