Repository navigation
Drivine 0.3.0 - #72
Merged
Merged
Conversation
Moves Drivine from 0.2.0 to 0.3.0, in step with dice and embabel-chat-store. 0.3.0 drops the compiled constructor that a Kotlin call to UniquenessConstraintSpec with a defaulted argument links to, so this library built on 0.2.0 fails with NoSuchMethodError on 0.3.0. No source changes.
…earch needs on Drivine 0.3.0 Since Drivine 0.3.0 a vector search through a partition label returns only the nodes that carry the fragment's labels (liberation-data/drivine4j#247). The probe's nodes carried RecallProbe alone, so its three searches came back empty. They now carry Chunk and ContentElement too, and the KDoc says why. Test-only: production code never searches through a partition label.
jasperblues
marked this pull request as ready for review
October 26, 2026 02:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves Drivine from 0.2.0 to 0.3.0, in step with dice and embabel-chat-store. A host resolves one Drivine.
Draft until drivine4j 0.3.0 is published. The pom names
0.3.0, which isn't on Maven Central yet, so CI fails to resolve it until then.Why
Drivine 0.3.0 drops the compiled constructor that a Kotlin call to
UniquenessConstraintSpecwith a defaulted argument links to.GraphObjectManagerStoremakes one (UniquenessConstraintSpec(properties.entityNodeName, "id")), so this library built on 0.2.0 fails withNoSuchMethodErroron a host that runs 0.3.0.No production changes were needed.
GraphProvisionerandEntitySchemaProvisionerensure their indexes directly rather than through a catalog, so 0.3.0's refusal of a catalog vector index over a field without@VectorIndex(liberation-data/drivine4j#132) doesn't apply to them, andChunkNodeandEntityNodecarry the annotation anyway.A test change
On released 0.3.0, the three tests in
Neo4jVectorRecallSearchKTestcame back empty. Since 0.3.0 a vector search through a partition label returns only the nodes that carry the fragment's labels (liberation-data/drivine4j#247, fixed in #254). The probe's nodes carriedRecallProbealone. They now carryChunkNode's labels,ChunkandContentElement, too, and the KDoc says why. Production code never searches through a partition label. The probe still deletes its nodes in@AfterAll, and test classes run one at a time.Tested
Against released drivine4j 0.3.0 (tag
0.3.0), installed locally:mvn installis green, 489 tests, 0 failures. Recall@40 is 0.95 unfiltered without searchK and 1.0 with searchK=200; tenant-filtered, 25/40 and 40/40.