You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run this query again to see that pred2 and pred3 were deleted and the result is empty.
{
test(func: has(pred2)) {
uid
pred2
pred3
}
}
Expected behavior and actual result.
When executing mutation from step 4 with a wildcard on the predicate, the predicates are not deleted. I would expect mutation from step 4 to have the same outcome as mutation from step 6 that uses explicit predicates as documented here.
Additional information
No response
The text was updated successfully, but these errors were encountered:
That explains it. However, it would be great to add or reference this in the documentation about Deleting Data as well: https://dgraph.io/tour/schema/8/
So will the wildcard then only delete the predicates that are defined for the type?
What version of Dgraph are you using?
v23.0.1
Tell us a little more about your go-environment?
I'm using the
dgraph/dgraph:latest
image from dockerhub.Have you tried reproducing the issue with the latest release?
Yes
What is the hardware spec (RAM, CPU, OS)?
Fedora 38 Host
Intel Core i7 CPU
32GB RAM
What steps will reproduce the bug?
Set predicate type to
string
and enableindex
,upset
andhash
onid
in the schema.Run this query to see that
pred2
andpred3
exist:pred2
andpred3
still exist:pred2
andpred3
were deleted and the result is empty.Expected behavior and actual result.
When executing mutation from step 4 with a wildcard on the predicate, the predicates are not deleted. I would expect mutation from step 4 to have the same outcome as mutation from step 6 that uses explicit predicates as documented here.
Additional information
No response
The text was updated successfully, but these errors were encountered: