I see that the current snapshot of Neo4j uses version 1.5 of Gremlin: gremlin> Gremlin.version() ==> 1.5
Do you have a timeline for updating Gremlin to the newest version? The newer versions have great features that I'd like to try out (https://github.com/tinkerpop/gremlin/wiki/Release-Notes) both in web admin and via REST.
Amergin,
yes, I want to get this done before 1.9 GA. However, since we are
trying to be backwards compatible and there are a number of things
that make this update incompatible (especially indexing in Gremlin
2.1), the simple upgrades that we have been doing will not work. What
instead has to happen is:
- break out tinkerpop dpendencies from Neo4j Server into the Gremlin plugin
- make the Webadmin backend service load installed console services
via the Java Service loader, so that the Gremlin plugin can contribute
the Gremlin Console for the Webadmin
- provide 2 plugin versions (Gremlin 1.5 and Gremlin 2.1.0) so users
can update Neo4j, and choose to keep at Gremlin 1.5 in order to get a
working system before chosing to migrate.
This is a bit bigger than before, so we are trying to get this into
the first milestones. Working on it :)
On Thu, Oct 11, 2012 at 8:19 PM, Amergin <amergi...@gmail.com> wrote:
> I see that the current snapshot of Neo4j uses version 1.5 of Gremlin:
> gremlin> Gremlin.version()
> ==> 1.5
> Do you have a timeline for updating Gremlin to the newest version? The newer
> versions have great features that I'd like to try out
> (https://github.com/tinkerpop/gremlin/wiki/Release-Notes) both in web admin
> and via REST.
Just a massive +1 for this integration, since I've gone and rashly written a big load of code that depends on Frames 2.1.0 and the Blueprints stack, and I'm terrified of having to maintain my own patched Community version for any length of time!
On Thursday, 11 October 2012 20:26:44 UTC+1, Peter Neubauer wrote:
> Amergin, > yes, I want to get this done before 1.9 GA. However, since we are > trying to be backwards compatible and there are a number of things > that make this update incompatible (especially indexing in Gremlin > 2.1), the simple upgrades that we have been doing will not work. What > instead has to happen is:
> - break out tinkerpop dpendencies from Neo4j Server into the Gremlin > plugin > - make the Webadmin backend service load installed console services > via the Java Service loader, so that the Gremlin plugin can contribute > the Gremlin Console for the Webadmin > - provide 2 plugin versions (Gremlin 1.5 and Gremlin 2.1.0) so users > can update Neo4j, and choose to keep at Gremlin 1.5 in order to get a > working system before chosing to migrate.
> This is a bit bigger than before, so we are trying to get this into > the first milestones. Working on it :)
> On Thu, Oct 11, 2012 at 8:19 PM, Amergin <amer...@gmail.com <javascript:>> > wrote: > > I see that the current snapshot of Neo4j uses version 1.5 of Gremlin: > > gremlin> Gremlin.version() > > ==> 1.5
> > Do you have a timeline for updating Gremlin to the newest version? The > newer > > versions have great features that I'd like to try out > > (https://github.com/tinkerpop/gremlin/wiki/Release-Notes) both in web > admin > > and via REST.
On Monday, October 29, 2012, Mike Bryant <mikesn...@gmail.com> wrote:
> Just a massive +1 for this integration, since I've gone and rashly
written a big load of code that depends on Frames 2.1.0 and the Blueprints
stack, and I'm terrified of having to maintain my own patched Community
version for any length of time!
> On Thursday, 11 October 2012 20:26:44 UTC+1, Peter Neubauer wrote:
>> Amergin,
>> yes, I want to get this done before 1.9 GA. However, since we are
>> trying to be backwards compatible and there are a number of things
>> that make this update incompatible (especially indexing in Gremlin
>> 2.1), the simple upgrades that we have been doing will not work. What
>> instead has to happen is:
>> - break out tinkerpop dpendencies from Neo4j Server into the Gremlin
plugin
>> - make the Webadmin backend service load installed console services
>> via the Java Service loader, so that the Gremlin plugin can contribute
>> the Gremlin Console for the Webadmin
>> - provide 2 plugin versions (Gremlin 1.5 and Gremlin 2.1.0) so users
>> can update Neo4j, and choose to keep at Gremlin 1.5 in order to get a
>> working system before chosing to migrate.
>> This is a bit bigger than before, so we are trying to get this into
>> the first milestones. Working on it :)
>> On Thu, Oct 11, 2012 at 8:19 PM, Amergin <amer...@gmail.com> wrote:
>> > I see that the current snapshot of Neo4j uses version 1.5 of Gremlin:
>> > gremlin> Gremlin.version()
>> > ==> 1.5
>> > Do you have a timeline for updating Gremlin to the newest version? The
newer
>> > versions have great features that I'd like to try out
>> > (https://github.com/tinkerpop/gremlin/wiki/Release-Notes) both in web
admin
>> > and via REST.
On Monday, 29 October 2012 19:45:14 UTC-7, Peter Neubauer wrote:
> It's on the backlog for 1.9 so i am positive :-)
> /peter
> On Monday, October 29, 2012, Mike Bryant <mike...@gmail.com <javascript:>> > wrote: > > Just a massive +1 for this integration, since I've gone and rashly > written a big load of code that depends on Frames 2.1.0 and the Blueprints > stack, and I'm terrified of having to maintain my own patched Community > version for any length of time!
> > No pressure Peter! ;)
> > On Thursday, 11 October 2012 20:26:44 UTC+1, Peter Neubauer wrote:
> >> Amergin, > >> yes, I want to get this done before 1.9 GA. However, since we are > >> trying to be backwards compatible and there are a number of things > >> that make this update incompatible (especially indexing in Gremlin > >> 2.1), the simple upgrades that we have been doing will not work. What > >> instead has to happen is:
> >> - break out tinkerpop dpendencies from Neo4j Server into the Gremlin > plugin > >> - make the Webadmin backend service load installed console services > >> via the Java Service loader, so that the Gremlin plugin can contribute > >> the Gremlin Console for the Webadmin > >> - provide 2 plugin versions (Gremlin 1.5 and Gremlin 2.1.0) so users > >> can update Neo4j, and choose to keep at Gremlin 1.5 in order to get a > >> working system before chosing to migrate.
> >> This is a bit bigger than before, so we are trying to get this into > >> the first milestones. Working on it :)
> >> On Thu, Oct 11, 2012 at 8:19 PM, Amergin <amer...@gmail.com> wrote: > >> > I see that the current snapshot of Neo4j uses version 1.5 of Gremlin: > >> > gremlin> Gremlin.version() > >> > ==> 1.5
> >> > Do you have a timeline for updating Gremlin to the newest version? > The newer > >> > versions have great features that I'd like to try out > >> > (https://github.com/tinkerpop/gremlin/wiki/Release-Notes) both in > web admin > >> > and via REST.
