You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This approach works fine for retrieving 3-10 records, but it becomes impractical for 100-1000 records, taking minutes or even hours.
Using getVertices:
I will get all the records, But this method is not suitable when dealing with vertex that have more than 1 million records.
Suggested Solution:
To improve efficiency, I propose creating a GSQL query that accepts a vertex and an ID list, returning the target vertices. This would be significantly more efficient.
Request:
Please consider replacing the getVerticesById function with a method that utilizes this GSQL query. This would eliminate the need for me to support such a query on my end.
The text was updated successfully, but these errors were encountered:
I want to retrieve large amount of records from a vertex.
Currently my 2 options are:
getVerticesById
:I will get the records I need, But this method sends GET requests in a loop:
This approach works fine for retrieving 3-10 records, but it becomes impractical for 100-1000 records, taking minutes or even hours.
getVertices
:I will get all the records, But this method is not suitable when dealing with vertex that have more than 1 million records.
Suggested Solution:
To improve efficiency, I propose creating a GSQL query that accepts a vertex and an ID list, returning the target vertices. This would be significantly more efficient.
Request:
Please consider replacing the getVerticesById function with a method that utilizes this GSQL query. This would eliminate the need for me to support such a query on my end.
The text was updated successfully, but these errors were encountered: