-
Notifications
You must be signed in to change notification settings - Fork 252
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
Is CQEngine officially dead? #323
Comments
Yeah, there is no activity. AFAIR, there is an issue in the Kryo version, which is not supported by Java 17. If you are interested in JVM 17 support, I made those changes two years ago (see #324) and forgot to share them |
Sad to see it neglected, it was my go-to for solving many performance bottlenecks and I just came back to it after a couple of years to investigate solving a new issue. I will investigate how much effort it will be to replace Kryo with a more supported serializer (perhaps eclipsestore?) |
@emrul, it looks like Kryo is well supported (see releases). It goes a bit behind JDK releases but keeps the pace. Its CQEngine has had no Kryo updates for a long time. But if we are talking about serializers, I think it is worth looking in Apache Fury. |
Well, I'm not ready to let go of this project - first priority is to keep it up to date with respect to Java versions and vulnerabilities. using @lvitaly's work as a starting point I updated it and have all tests passing on JDK21. Also updated SQLite (#319) and Guava. https://github.com/emrul/cqengine/tree/feature/jdk-21 I had to use the workaround described here to get past the restrictive reflection errors so that'll probably limit the use in some Java environments >=17 for now :-( |
In my fork the Maven Shade plugin seems to hang now - even when running it in debug mode there's no warnings/errors. I disabled the shade plugin and it seems to work... so more investigation required. |
Hi I have in mind tasks like moving to GitHub action, jdk21 or more, maven upgrade, lib upgrades, antlr ... Thx |
I believe this project has great potential, but it would be even better if it could be actively maintained with updates like those mentioned above. Any news? |
I see that there is no activity on this project since last year. Seems author became inactive on Github since that time as well (hopefully he is fine and nothing serious happened in his life).
BTW, compatibility issues started to appear here (e.g. JVM 17). Highly likely some serious bugs and security issues may be identified in nearest future, especially in transitive dependencies. It becomes unsafe to use the stale project.
Is there anybody who is capable of taking care of this project in nearest future? Or may it be considered officially dead and abandoned?
If the latest, who can advise any good alternatives for it?
The text was updated successfully, but these errors were encountered: