thanks, this worked!
On Monday, May 4, 2015 at 9:18:42 AM UTC-4, Khaled B wrote:
>
> Hey,
>
> Orientdb indexes' implementation is different than the one used by
> Tinkerpop .
>
> So, in gremlin, to get a vertex by index, do the following :
>
> instead of
>
> u= g.V('Person.personid',7409070)
>
>
> use this ( uses Orientdb's index manager) :
>
> u= g.v(g.getRawGraph().getMetadata().getIndexManager().getIndex(
> 'Person.personid').get(7409070))
>
>
>
>
> On Friday, May 1, 2015 at 11:03:05 PM UTC+3, sck2015 wrote:
>>
>> Hi, I saw a posting that this bug was resolved post community edition
>> 2.0.9, I just downloaded the latest snapshot 2.1-SNAPSHOT and am still
>> seeing the issue thru gremlin as well as the javaapi using the
>> g.getVertices command...
>> so for example:
>> gremlin> g.V.has('personid',7409070)
>>
>> gremlin> g.V('personid',7409070)
>> gremlin> g.V('Person.personid',7409070)
>>
>> don't work even though that class and attribute (a long) do exist in the
>> database, looking up by a string valued attribute works, please advise if
>> resolved or work around (doesn't matter whether the attribute is indexed or
>> not, problem in lookup happens either way).
>>
>
--
---
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.
