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
OS: macOS Monterey 12.1, MacBook Pro (16-inch, 2019)
CPU: Intel Core i7, 6 cores, 2.6 GHz
Nebula Graph Version: nebula-docker-compose v3.0.1 modified with 1 metad, 1 storaged and 1 graphd
How To Reproduce
Steps to reproduce the behavior:
Create a graph as follow: ds1 -> j1 -> ds2 -> j2 -> ds3
# create space
CREATE SPACE IF NOT EXISTS test(vid_type=FIXED_STRING(20));
USE test;
# create schema
CREATE TAG IF NOT EXISTS dataset();
CREATE TAG IF NOT EXISTS job();
CREATE EDGE IF NOT EXISTS lineage();
CREATE TAG INDEX IF NOT EXISTS dataset_index on dataset();
CREATE TAG INDEX IF NOT EXISTS job_index on job();
CREATE EDGE INDEX IF NOT EXISTS lineage_index on lineage();
REBUILD TAG INDEX dataset_index;
REBUILD TAG INDEX job_index;
REBUILD EDGE INDEX lineage_index;
# insert data
INSERT VERTEX dataset() VALUES "ds1":();
INSERT VERTEX dataset() VALUES "ds2":();
INSERT VERTEX dataset() VALUES "ds3":();
INSERT VERTEX job() VALUES "j1":();
INSERT VERTEX job() VALUES "j2":();
INSERT EDGE lineage() VALUES "ds1" -> "j1":(), "j1" -> "ds2":(), "ds2" -> "j2":(), "j2" -> "ds3":();
r9liucc
changed the title
Unexpected relationship direction in MATCH...WHERE... query result
Unexpected edge direction in MATCH...WHERE... query result
Mar 17, 2022
Environments
macOS Monterey 12.1, MacBook Pro (16-inch, 2019)
Intel Core i7, 6 cores, 2.6 GHz
nebula-docker-compose v3.0.1
modified with 1 metad, 1 storaged and 1 graphdHow To Reproduce
Steps to reproduce the behavior:
ds1 -> j1 -> ds2 -> j2 -> ds3
Expected behavior
The
ds2
should have an incoming direction edge started fromj1
, which was expected inQuery A
, butQuery B
has a contrary result.The text was updated successfully, but these errors were encountered: