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

Gremlin: Enhance performance of reuse graph traversal source #7

Open
chungquantin opened this issue Dec 2, 2022 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@chungquantin
Copy link
Owner

Is your feature request related to a problem? Please describe.

let t1 = db
		.traverse()
		.v(1)
		.add_v("person")
		.property("github", "tin-snowflake")
		.property("name", "Tin Chung")
		.property("age", 21)
		.add_v("coder")
		.property("github", "chungquantin")
		.property("age", 30);

let t2 = t1.clone().has_key("github").has_label("person").exec().to_list().await.unwrap();
let t3 = t1.clone().has_key("github").exec().to_list().await.unwrap();
let t4 = t1.clone().has_not("name").exec().next().await.unwrap();

Describe the solution you'd like
For now, query like this is exhaustive. Even though t1 is reused, all steps are handled again whenever t2, t3 or t4 called. Can implement a record checkpoint to enhance the situation

@chungquantin chungquantin added the enhancement New feature or request label Dec 2, 2022
@chungquantin chungquantin added this to the Gremlin Compatibility milestone Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant