-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Labels
Effort - UnknownEffort - UnknownEffort - UnknownFrequency - EveryTimeFrequency - EveryTimeFrequency - EveryTimeReach - SomeReach - SomeReach - SomeSeverity - S2Severity - S2Severity - S2bugbugbugcommunitycommunitycommunity
Description
Describe the bug
In the documentation, examples for subgraph_all
are given. Unfortunately, they don't work as described.
To Reproduce
Run the following query:
CREATE (w:Wolf)-[ca:CATCHES]->(d:Dog), (c:Cat), (m:Mouse), (h:Human);
MATCH (w:Wolf), (d:Dog), (c:Cat), (m:Mouse), (h:Human)
WITH w, d, c, m, h
CREATE (d)-[:CATCHES]->(c)
CREATE (c)-[:CATCHES]->(m)
CREATE (d)-[:FRIENDS_WITH]->(m)
CREATE (h)-[:OWNS]->(d)
CREATE (h)-[:HUNTS]->(w)
CREATE (h)-[:HATES]->(m);
MATCH (dog:Dog)
CALL path.subgraph_all(dog, {
labelFilter: ["/Mouse"]
})
YIELD nodes AS nodes, rels AS rels
RETURN nodes, rels
This returns only a single node, Mouse
:
{
"nodes": [
{ "id": 13, "labels": ["Mouse"], "properties": {}, "type": "node" }
],
"rels": []
}
Expected behavior
According to the documentation, this filtering will return 3 paths: Dog->Cat->Mouse
, Dog<-Human->Mouse
, Dog->Mouse
.
Additional context
I tried this in the newest Memgraph version 3.2.1.
Metadata
Metadata
Assignees
Labels
Effort - UnknownEffort - UnknownEffort - UnknownFrequency - EveryTimeFrequency - EveryTimeFrequency - EveryTimeReach - SomeReach - SomeReach - SomeSeverity - S2Severity - S2Severity - S2bugbugbugcommunitycommunitycommunity
Type
Projects
Status
No status