-
Notifications
You must be signed in to change notification settings - Fork 338
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
committing delete query throws UNKNOWN #4447
Comments
@lolski just to give you some context on how the BLAST example(and its timeline) is associated with this bug: the part of the BLAST code that is blocked by this, is not the main part of the code and can be left out till this bug is fixed. We're planning to:
If you've too much on your hand, it's completely fine. we don't have to have that part of the BLAST example for these 2 milestones. |
Just ran into this exact issue. Is there a workaround for this or do deletes just not work in Grakn 1.4.2? |
Can you post the reproducible step using your data and query, @BFergerson ? Is it deterministic or non-deterministic? It's always good to have more data. |
@lolski, sure thing. Please check out this branch: https://github.com/bfergerson/grakn-calendar-test/tree/delete-test Running it causes:
|
@BFergerson thanks, we will have a look at it. |
@haikalpribadi, noticed you pushed this back to 1.6. Does that mean that delete queries won't in Grakn 1.5 as well? |
I actually haven't had a chance to look into this, @BFergerson. All the unresolved issues from 1.5 milestone were moved to 1.6 in batch. Is this something critical in your current usage? @flyingsilverfin can you help look into this issue? |
@haikalpribadi, it would definitely be nice to have. I've been wanting to bring the next iteration of GitDetective and the new model (discussed it here https://discuss.grakn.ai/t/modeling-time-based-graphs-in-grakn/996) would require deleting relationships. |
Alright, we'll look into it this week, @BFergerson ! :) |
So I've tried to reproduce @BFergerson nice small example - migrated to a relatively current version of 1.5 that we're close to releasing in a new repository (https://github.com/flyingsilverfin/grakn-debug/tree/master/delete-failure-brandon). I ran the test and it does not fail. @BFergerson you can try to update to 1.5 a bit early and build it directly, or wait a week and confirm it fixes your bug, and if not we can take look at it again and try to fix it for 1.5.1? |
@sorsaffari is going to check if the delete bug from Biograkn also disappears when using a current 1.5 server as well :) |
@BFergerson seems like it is happening in BioGrakn - will investigate further! |
@flyingsilverfin, thanks for looking into this. Out of curiosity, how would I download an early build of Grakn 1.5? Is that the master branch? |
Yes, @BFergerson. Just clone |
## What is the goal of this PR? Prevent Grakn from failing when deleting inferred concepts (specifically found to fail when deleting inferred relationships) Closes #4447 ## What are the changes implemented in this PR? Add a small `if` check during the delete process of a concept so that it is silently skipped if deleting an inferred concept.
@BFergerson I've fixed the original BioGrakn issue, which stemmed from trying to delete inferred concepts - please open a new issue if you keep having issues! |
Don't forget to move an issue to the correct milestone when you close it (and it wasn't originally in the correct one), @flyingsilverfin - thanks! |
Grakn version: 1.5.0-SNAPSHOT
Expected output:
Actual output
Reproducing
The text was updated successfully, but these errors were encountered: