-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
hibernate-vector integration (through version management OR extension) #41453
Comments
If it works out of the box, we can just include it in the BOM. Does it though? :) |
Yes it works, the only thing is that you need to know beforehand the Hibernate version used by Panache. |
Right, we don't necessarily need a separate extension, a BOM entry would be fine as a first step. The patch is trivial, testing... not so much. I'd need a separate integration test module just for this... including a native build. @gsmet are you fine with that? |
Let's assume @gsmet is fine with that and add an IT module for pgvector, at least :) Note we'll need to document this as supported as well. |
Description
Currently (or at least what I've found), to use the
hibernate-vector
dependency, you need to add the version of Hibernate manually.This means you need to explore which Hibernate version is transitively imported by Panache and then hardcoded in the pom.
So, if I update the Quarkus version to a newer version, and the Hibernate version used by Panache is updated too, then my pom might have a divergence in versions.
Implementation ideas
Create an extension that just imports the correct
hibernate-vector
or a Panache bom so the version of Hibernate is implicitly set.The text was updated successfully, but these errors were encountered: