bamaer opened a new issue, #9079:
URL: https://github.com/apache/hop/issues/9079

   ### What needs to happen?
   
   Update the drivers and container images used by the graph database plugins 
and their tests, and fix the version references in the docs.
   
   ### Libraries
   
   - Lettuce `6.8.2.RELEASE` → `7.9.0.RELEASE` in `plugins/tech/falkordb` and 
`plugins/tech/redis` (the two plugins share the same client). Lettuce 7.x is 
built on Netty 4.2 and Reactor 3.8, the versions Hop already ships in 
`lib/core`.
   
   No change needed for the Neo4j Java driver (6.3.0), the TinkerPop 
gremlin-driver (3.7.7, the latest 3.7.x), janusgraph-driver (1.1.0) or the 
PostgreSQL JDBC driver (42.7.14). TinkerPop 3.8 waits until JanusGraph 1.2.0 is 
released.
   
   ### Container images
   
   | Image | From | To | Where |
   |---|---|---|---|
   | `memgraph/memgraph` | 3.6.0 | 3.13.2 | `integration-tests-memgraph.yaml`, 
`MemgraphBoltIT` |
   | `falkordb/falkordb` | 6.0.1 | 6.0.2 | `integration-tests-falkordb.yaml`, 
`FalkorDbIT` |
   | `tinkerpop/gremlin-server` | 3.7.6 | 3.7.7 (matches the driver) | 
`integration-tests-gremlin.yaml`, `GremlinServerIT` |
   | `neo4j` | 2026.06.0-enterprise | 2026.09.0-enterprise | 
`integration-tests-neo4j.yaml`, `integration-tests-neo4j-bolt.yaml` |
   
   `apache/age:release_PG18_1.8.0` and `janusgraph/janusgraph:1.1.0` are 
already the latest.
   
   ### Docs
   
   `technology/graph-databases/index.adoc` has the wrong release numbers in the 
upgrade section: "Upgrading from Hop 2.20 or earlier" should say 2.19, and 
"From Hop 2.21 on" should say 2.20.
   
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: Metadata, Component: Actions, Component: Transforms, Component: 
Documentation


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to