Traversing that involve super node

i am using database version 4.3.3, for the below query that involve a supernode. While finding path between user u1 and u3 a super node comes. On profiling i am not able to understand why query engine doesn't check for supernode.

CREATE INDEX username_index FOR (u:User) ON (u.name);
MATCH (n) DETACH DELETE n;
CREATE (u1:User {name: 'u1'}),
(u2:User {name: 'u2'}),
(u3:User {name: 'u3'}),
(u4:User {name: 'u4'}),
(u5:User {name: 'u5'}),
(u6:User {name: 'u6'}),
(u7:User {name: 'u7'}),
(u8:User {name: 'u8'}),
(u9:User {name: 'u9'}),
(sperNode:User {name: 'super-node'}),
(u1) -[:FOLLOWS]-> (u2),
(u2) -[:FOLLOWS]-> (u3),
(u2) -[:FOLLOWS]-> (sperNode),
(u4) -[:FOLLOWS]-> (sperNode),
(u5) -[:FOLLOWS]-> (sperNode),
(u6) -[:FOLLOWS]-> (sperNode),
(u7) -[:FOLLOWS]-> (sperNode),
(u8) -[:FOLLOWS]-> (sperNode),
(u9) -[:FOLLOWS]-> (sperNode)
RETURN *

PROFILE
MATCH (u1:User { name: "u1" })
WITH u1
MATCH p=(u1)-[:FOLLOWS*]-(:User { name: "u3" })
RETURN p

Thanks in advance,
baseer

may be because "super-node" ist not on any path between u1 and u3?
Untitled graph (1)

Even if i add super node in the path from user u1 to u3 , then also it will not check for all the relationship of supernode. though its performance magic of cypher query engine in optimising search path.

test data; super node in path

CREATE  (u1:User {name: 'u1'}),
        (u2:User {name: 'u2'}),
        (u3:User {name: 'u3'}),
        (u4:User {name: 'u4'}),
        (u5:User {name: 'u5'}),
        (u6:User {name: 'u6'}),
        (u7:User {name: 'u7'}),
        (u8:User {name: 'u8'}),
        (u9:User {name: 'u9'}),
        (sperNode:User {name: 'super-node'}),
        (u1) -[:FOLLOWS]-> (u2),
        (u2) -[:FOLLOWS]-> (u3),
        (u2) -[:FOLLOWS]-> (sperNode),
(sperNode) -[:FOLLOWS]-> (u3),

        (u4) -[:FOLLOWS]-> (sperNode),
        (u5) -[:FOLLOWS]-> (sperNode),
        (u6) -[:FOLLOWS]-> (sperNode),
        (u7) -[:FOLLOWS]-> (sperNode),
        (u8) -[:FOLLOWS]-> (sperNode),
        (u9) -[:FOLLOWS]-> (sperNode)
RETURN *

Still supernode relationships are not checked. In my understanding, supernode should degrades performance. That's the reason i had not specified the directionality in below query.

PROFILE
MATCH p = (u1:User { name: "u1" })-[r1:FOLLOWS*]-(u3:User { name: "u3" })
RETURN p

Screenshot 2021-09-16 at 9.45.59 AM

Hi!

Can you define check for a super node?

Bennu

i expect query engine checking all relationships of super node if its on the path between user u1 and u3 using below query (direction of relationship not mentioned)

PROFILE
MATCH p = (u1:User { name: "u1" })-[r1:FOLLOWS*]-(u3:User { name: "u3" })
RETURN p