The results of pattern match gremlin query only returns 64 vertices when there are 91 that match the query

0
votes

I am running a gremlin match query that limits the results based on the value of some of the properties of the graph. When I run the query in the gremlin console I get 91 vertices that match the pattern. When I run the same query through a javascript websocket connection I get only 64 returned. If I add .count() to the query I get the 91 expected. Is there a setting to allow all the results to be retrieved?

g.V().match(__.as('Patient').hasLabel('Patient').has('gender',eq('Male')).has('birth_date',gt(Date.parse('yyyy-mm-dd','1970-01-01'))).has('adoptee',true)).select('Patient')

Should get 91 but instead get

(64) [{…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}]

1
websocketgremlinjanusgraph

1 Answers

1
votes

64 is an interesting number. It is the default setting for resultIterationBatchSize in the Gremlin Server yaml file. Try to increase that and see if that fixes the problem. That said, you shouldn't have to do that as that setting just means that if the result exceeds 64 items then another batch of 64 should follow until the result is completed. There may have been a bug related to that with Gremlin Javascript at some point - if you can recreate the problem on the latest version you may need to create an issue in JIRA.