Skip to content
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

Multiple edgetype, go statement behavior #2314

Closed
panda-sheep opened this issue Aug 24, 2020 · 1 comment
Closed

Multiple edgetype, go statement behavior #2314

panda-sheep opened this issue Aug 24, 2020 · 1 comment
Assignees
Labels
type/bug Type: something is unexpected
Milestone

Comments

@panda-sheep
Copy link
Contributor

panda-sheep commented Aug 24, 2020

use case:

CREATE TAG DID(did string);
CREATE TAG UID(uid string);

INSERT VERTEX DID (did) VALUES 11:("n2");
INSERT VERTEX DID (did) VALUES 13:("n22");

INSERT VERTEX UID (uid) VALUES 11:("n3");
INSERT VERTEX UID (uid) VALUES 13:("n33");

CREATE EDGE GID_DID(create_time timestamp,update_time timestamp);   
CREATE EDGE GID_UID(create_time timestamp,update_time timestamp);  

INSERT EDGE GID_UID(create_time, update_time) VALUES 11->13: (1597914255, 1597680000);
INSERT EDGE GID_DID(create_time, update_time) VALUES 11->13: (1597914255, 1597680000);

go from 11 over GID_UID,GID_DID where GID_UID.update_time >= 1597680000 or GID_DID.update_time >= 1597680000; (1) go from 11 over GID_UID,GID_DID where GID_UID.update_time >= 1597680000 ; (2)
What is the expected behavior of the go statement?

before nebula 1.0.1
image

master in nebula 1.0
image

@panda-sheep
Copy link
Contributor Author

The pr involved is
#2235

@panda-sheep panda-sheep added the type/bug Type: something is unexpected label Aug 24, 2020
@jude-zhu jude-zhu added this to the v1.0.2 milestone Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

3 participants