Closed szarnyasg closed 3 years ago
It turns out my .graph
file was indeed incorrect and (I mixed up target the vertex labels for some edges in my conversion script).
I'm leaving the issue open if you'd like to investigate with the example file -- but feel free to close this issue.
It turns out my
.graph
file was indeed incorrect and (I mixed up target the vertex labels for some edges in my conversion script). I'm leaving the issue open if you'd like to investigate with the example file -- but feel free to close this issue.
Hi,
Thanks for your question.
Do you mean that the issue is caused by the script and the program works well after fixing the script? If so, I will close the issue. If not, could you please provide me the test case such that I can repro the problem and fix it?
@shixuansun Yes – I fixed the conversion script, now RapidMatch can load the graph and produce the correct results.
@shixuansun Yes – I fixed the conversion script, now RapidMatch can load the graph and produce the correct results.
OK. Thanks for your update. Then, I will close this issue.
Hi,
I'm trying to load an LDBC-based data file to RapidMatch: https://www.dropbox.com/s/cqebtyvms07h6rv/ldbc-0.1.graph.zip?dl=0
This command spinlocks on
Load graphs
and is not killed even after the timeout passes.I tried various settings such as turning preprocesing on, adding
nd
ordering but these did not make a difference.It is possible that there is an error in the
.graph
query file but I'm unable to pinpoint it.Is there a verbose/debug configuration for RapidMatch that I could activate to figure out where and why this spinlock occurs?
Gabor