, 2023 at 6:37 AM
To: dev@tinkerpop.apache.org
Subject: Re: [DISCUSS] Future of Neo4J-Gremlin
Thanks, Cole. I think that plan (deprecating Neo4j-Gremlin, but not
removing it until it becomes a nuisance) is a nice middle ground. Again
with the disclaimer that I am just one developer talking about his
hanks,
>
> Cole
>
> From: Joshua Shinavier
> Date: Thursday, July 20, 2023 at 4:21 PM
> To: dev@tinkerpop.apache.org
> Subject: Re: [DISCUSS] Future of Neo4J-Gremlin
> Deprecating Neo4j support in Gremlin would definitely mark the end of an
> era. I would be inclined to
not at that time it would need to be
removed.
Let me know your thoughts on this suggestion.
Thanks,
Cole
From: Joshua Shinavier
Date: Thursday, July 20, 2023 at 4:21 PM
To: dev@tinkerpop.apache.org
Subject: Re: [DISCUSS] Future of Neo4J-Gremlin
Deprecating Neo4j support in Gremlin would
gt;
> From: Cole Greer
> Date: Friday, July 14, 2023 at 2:38 PM
> To: Dev Tinkerpop
> Subject: [DISCUSS] Future of Neo4J-Gremlin
> Hi everyone,
>
> With the addition of transaction support in TinkerGraph in 3.7, I think
> now is a good time to reassess the Neo4J-Gremlin mod
] Future of Neo4J-Gremlin
Hi everyone,
With the addition of transaction support in TinkerGraph in 3.7, I think now is
a good time to reassess the Neo4J-Gremlin module. To the best of my knowledge,
Neo4J-Gremlin historically served 2 primary purposes. First it acted as a de
facto reference
Hi everyone,
With the addition of transaction support in TinkerGraph in 3.7, I think now is
a good time to reassess the Neo4J-Gremlin module. To the best of my knowledge,
Neo4J-Gremlin historically served 2 primary purposes. First it acted as a de
facto reference implementation of gremlin trans
