Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize search queries - id field select #22

Closed
eliranmoyal opened this issue Mar 16, 2015 · 4 comments
Closed

Optimize search queries - id field select #22

eliranmoyal opened this issue Mar 16, 2015 · 4 comments

Comments

@eliranmoyal
Copy link
Collaborator

when searching for elements we know we will not be asked about (used only for traversal)
we can only request the id of those fields.
meaning
if we ask for g.V().has("name","X").inE("knows").next()
we can only get the id from the first query - but not for the 2nd one.

The logic suggested is : if from your search until the next search there are not steps of kind:
propertyStep,identitiyStep(as("x"))
and the step is not the last search step. get only the id from elastic.

@rmagen
Copy link
Owner

rmagen commented Mar 18, 2015

isn't this a duplicate of #23?

@eliranmoyal
Copy link
Collaborator Author

this is a different optimization but probably have the same rules.
#23 talks about Vertex to Vertex queries which we don't need to really even fetch the vertices
here we talk about: when fetching the vertex/edge we could just fetch id field

@rmagen
Copy link
Owner

rmagen commented Mar 21, 2015

got ya, okay

@rmagen
Copy link
Owner

rmagen commented May 25, 2015

closed in favor of #47

@rmagen rmagen closed this as completed May 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants