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.

Sign up for GitHub

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

Jump to bottom

[Feat][Spark] Consider cache vertexDataFrame in VertexWriter #322

Closed
acezen opened this issue Jan 12, 2024 Discussed in #256 · 0 comments · Fixed by #326
Closed

[Feat][Spark] Consider cache vertexDataFrame in VertexWriter #322

acezen opened this issue Jan 12, 2024 Discussed in #256 · 0 comments · Fixed by #326

Comments

@acezen
Copy link
Contributor

acezen commented Jan 12, 2024

Discussed in #256

Originally posted by haohao0103 October 18, 2023
The vertexDataFrame obtained when the VertexWriter is created is convenient for subsequent jobs to use, whether to consider cache;
com.alibaba.graphar.writer.VertexWriter.scala
image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Feat][Spark] Memory tuning for GraphAr spark with persist and storage level acezen/GraphAr
1 participant
@acezen