Finally upgraded to 2.1 and seems like the problem is fixed.
I confirm you can't seem to create variables in this version. Previously I
could do it by first running a gremlin query without initializing the
variables (i.e. starting with g.V) and then when I get the variable doesn't
exist error, I can add the variables before the g.V and it would work. Now
I can create variables, but I have to do a dummy g.V query before my real
query, like so: g.V; users=[:]; g.V.sideEffect{users[it.id]=it}.iterate()
thanks for your help!
On Friday, April 3, 2015 at 1:01:49 AM UTC+2, Kyle wrote:
>
> I couldn't find any issues for the "gremlin closing the database" bug, so
> I created one here:
> https://github.com/orientechnologies/orientdb/issues/3866
>
> On Tuesday, March 31, 2015 at 10:42:08 AM UTC-7, Natal Kaplya wrote:
>>
>> I encountered the same problem after updated from 2.0.3 to 2.0.5, if you
>> update studio page, then connection is reestablished correctly, so after
>> every gremlin query you need to press f5. Database is not closed probably,
>> merely studio connection drops. I think it's a new bug, have to make an
>> issue on github.
>>
>> About creating a variable - there is no way to. Just use Rexster or
>> gremlin console app(inside orientdb is one).
>>
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
