Re: The count query based on the vertex traversal edges is too slow!!!
toggle quoted message Show quoted text
You are right, when the index is not used in the outV() step, Janugraph resorts to a full table scan until it has enough results, 10 in the first case and 30.010 in the second. Can you also try my other suggestion to first get the targetIds and use these in you main query? My hope is that the inE() step is sufficiently fast. The edges returned from inE() already contain the vertex id's that can be matched locally against targetIds.
Op maandag 26 oktober 2020 om 08:21:32 UTC+1 schreef wan...@...: