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

Unable to load Rel Table from Kuzu shell #1112

Closed
anuchak opened this issue Dec 12, 2022 · 1 comment · Fixed by #1179
Closed

Unable to load Rel Table from Kuzu shell #1112

anuchak opened this issue Dec 12, 2022 · 1 comment · Fixed by #1179
Assignees

Comments

@anuchak
Copy link
Collaborator

anuchak commented Dec 12, 2022

I'm trying to load the following two node and rel table, person and knows
The person csv gets loaded successfully but the rel csv gets stuck. I also tried after increasing memory, didn't work.

vPerson.csv
eKnows.csv

Commands used for defining table & loading csv:

create node table person (ID INt64, fName StRING, gender INT64, isStudent BoOLEAN, isWorker BOOLEAN, age INT64, eyeSight DOUBLE, birthdate DATE, registerTime TIMESTAMP, lastJobDuration interval, workedHours INT64[], usedNames STRING[], courseScoresPerTerm INT64[][], PRIMARY KEY (ID));

create rel table knows (FROM person TO person, date DATE, meetTime TIMESTAMP, validInterval INTERVAL, comments STRING[], MANY_MANY);

COPY person FROM "dataset/tinysnb/vPerson.csv" (HEADER=true);

COPY knows FROM "dataset/tinysnb/eKnows.csv";
@anuchak
Copy link
Collaborator Author

anuchak commented Jan 4, 2023

The bug seems to be a deadlock issue, same thread holding a shared_lock on the shared_mutex is trying to instantiate another unique_lock on the mutex.
Occurring when trying to add a new overflow page from in_mem_file.

@anuchak anuchak mentioned this issue Jan 6, 2023
@ray6080 ray6080 linked a pull request Jan 15, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants