I emailed Harsh about a year ago about this and didn't get a reply. I sense he has long moved on. I also think this isn't a case of someone stepping up to maintain it. The core element for making it work is match(Traversal) which is deprecated for 4.0, so that's a large hurdle to start for modernization. Given current direction, I don't think there's a strong need for a sparql-gremlin right now, modernized or not.
On Fri, May 8, 2026 at 5:43 PM Cole Greer via dev <[email protected]> wrote: > Hi everyone, > > I wanted to initiate a discussion around the removal of SPARQL-Gremlin in > TinkerPop 4. My primary reason for raising this is it has not been > maintained in a long time. The last non-trivial commit which touched it was > for TINKERPOP-2325 in January 2020. The core external dependency of > sparql-gremlin is Apache Jena, which we are currently pinned to version > 3.12.0 (from 2019). > > I'm concerned with the idea of continuing to ship a module which is > unmaintained and has very limited testing. It's not at all clear to me how > well this module continues to function, if at all. If we wish to retain > SPARQL-Gremlin, I would argue that we need a committer to step forward and > champion it's ongoing maintenance, and it should get modernized to a later > version of Jena (which itself is an issue as Jena 5 requires Java 17, and > Jena 6 requires Java 21). > > If no one is interested in taking on this modernization and maintenance, I > believe the best course of action is to remove the module entirely as of > TinkerPop 4. > > Please let me know if you have any thoughts on this, especially if you > currently rely on SPARQL-Gremlin and/or are interested in championing it's > modernization and maintenance. > > Thanks, > Cole >
