Issue while retrieving edge

[Amiya]

Hi,

I am facing some weird issue. Till now I discovered only for one vertex.

There is a particular vertex having 30K edges. 

When I try to fetch some number of edges among them, sometime I get edges exactly less by 1 number.

g.V().has('vid', 'xyz').bothE().count()

==> 30000 

g.V().has('vid', 'xyz').bothE().limit(5000).count()  

==> 4999

When I try with some other number of samples, It returns correct result upto a point let's say 3500. After that problem occurs.

That means if I say fetch 3500 or 3501, I get 3500 records only.

How it can happen? Anyone faced before? What is the solution? 

Regards,

Amiya

[Raghavendar T S]

Hi

I have seen a similar behaviour in Datastax Graph/Cassandra. Basically If you are going to query using gremlin query (E.g. valueMap()), the graph engine will convert the gremlin query into cassandra query with max default limit 50000. Basically you cannot retrieve the results beyond the limit 50000 though your filter condition matches more than 50000 records. Still count transversal will work to return valid results where the default limit is not added by the graph engine. Correct me If I am wrong.

@Amiya We will look for more appropriate answers.

Thank you

--
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/d50df1b0-89f6-4d6c-a3dd-8ed3c67144e4n%40googlegroups.com.

--

Raghavendar T S

www.teknosrc.com

[Amiya]

Thanks Raghavendar for the response.
For my uses case, I see this issue only for one vertex with lower count such as 3500, graph provides correct result for other vertex even with large number than this.

It might be some issue at storage layer, I will try to dig it further with debug log enabling, if I found anything I will post it back.

Amiya