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
predicate is not deleted from "_predicates_" #2484
Comments
tested on 1.0.6 - the same behaviour, so updated issue with that |
I'm able to reproduce this, it seems to me related to #2212 If I do (this is after delete): {
result(func: eq(entity_key, "entity1")) {
uid
_predicate_
entity_key
has {expand(_all_)}
}
result2(func: has(has)) {
uid
_predicate_
entity_key
has {expand(_all_)}
}
} Returns: {
"data": {
"result": [
{
"_predicate_": [
"has",
"entity_key"
],
"uid": "0x5",
"entity_key": "entity1"
}
],
"result2": [
{
"_predicate_": [
"has",
"entity_key"
],
"uid": "0x5",
"entity_key": "entity1"
}
]
} before delete: {
"data": {
"result": [
{
"_predicate_": [
"has",
"entity_key"
],
"uid": "0x5",
"entity_key": "entity1",
"has": [
{
"entity_key": "entity2"
}
]
}
],
"result2": [
{
"_predicate_": [
"has",
"entity_key"
],
"uid": "0x5",
"entity_key": "entity1",
"has": [
{
"entity_key": "entity2"
}
]
}
]
}
|
This is partially fixed. By #2585 . In theory this fix would not have side effects with the existence of "ghost" predicates in the Node. But it still need to clean them. A solution usage. {
result(func: has(has)) @filter(eq(entity_key, "entity1")) {
entity_key
uid
has {
uid
}
}
} or {
result(func: eq(entity_key, "entity1") ) @filter(has(has)) {
entity_key
uid
has {
uid
}
}
} |
The original issue with |
erro: |
If you suspect this could be a bug, follow the template.
What version of Dgraph are you using?
1.0.6
Have you tried reproducing the issue with latest release?
yes
Steps to reproduce the issue (command/config used to run Dgraph).
when I remove predicate - it doesn't disappear from _predicate_ field whereas actually it doesn't exist anymore.
"has" predicate should be removed from _predicate_
The text was updated successfully, but these errors were encountered: