acezen commented on issue #584:
URL:
https://github.com/apache/incubator-graphar/issues/584#issuecomment-2285440616
> I came across this issue and would love to help out. Is there any
additional information or context I should be aware of before I get started?
>
> Looking forward to contributing!
Hi, @SumitkumarSatpute , thanks for the interest to GraphAr. the generated
templary data is generated by unit tests of write:
- c++
-
[test_builder.cc](https://github.com/apache/incubator-graphar/blob/main/cpp/test/test_builder.cc)
-
[test_arrow_chunk_writer.cc](https://github.com/apache/incubator-graphar/blob/main/cpp/test/test_arrow_chunk_writer.cc)
- spark:
-
[testGraphWriter](https://github.com/apache/incubator-graphar/blob/00032420faf100299a857eacc882089a95a78202/maven-projects/spark/graphar/src/test/scala/org/apache/graphar/TestGraphWriter.scala#L48C1-L49C1)
-
[testWrtier](https://github.com/apache/incubator-graphar/blob/main/maven-projects/spark/graphar/src/test/scala/org/apache/graphar/TestWriter.scala)
So I think you need to clean the ouput directories like `/tmp/vertex`,
`/tmp/edge` , `/tmp/ldbc` base on the unit tests and clean them with the top
level `make clean` of the libraries.
Feel free to ask if you have any question and enjoy the trip:)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
