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.

Sign up for GitHub

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

Jump to bottom

how to get remote node id through a bidirectional edge #1767

Closed
whitewum opened this issue Feb 13, 2020 · 1 comment
Closed

how to get remote node id through a bidirectional edge #1767

whitewum opened this issue Feb 13, 2020 · 1 comment

Comments

@whitewum
Copy link
Contributor

whitewum commented Feb 13, 2020 •
edited
Loading

E.g.

(a:Person)-(b:Person)-(c:Person)-(d:Person)

the direction between a and b is irrelevant (either direction is OK to me).

Now, from node a, I want to get node b'id. How to represent it by the query language?

#1631
@CPWstatic
Copy link
Contributor

#1740 We would support bidirectional traverse.

@jude-zhu jude-zhu closed this as completed Mar 9, 2020
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Jan 31, 2023
@nebula-bots @codesigner
fix SubGraph edge type in filter does not exist in tranversed edge ty…
229179d 
…pe (vesoft-inc#1767)

## What type of PR is this?
- [x] bug
- [ ] feature
- [ ] enhancement

## What problem(s) does this PR solve?
#### Issue(s) number: 
fix vesoft-inc#4766 

#### Description:

As vesoft-inc#4766 described, query should failed with correct message. Added some check edge type during validation stage.

## How do you solve it?



## Special notes for your reviewer, ex. impact of this fix, design document, etc:



## Checklist:
Tests:
- [x] TCK
- [ ] Unit test(positive and negative cases)
- [ ] Function test
- [ ] Performance test
- [ ] N/A

Affects:
- [ ] Documentation affected (Please add the label if documentation needs to be modified.)
- [ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.）
- [ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
- [ ] Performance impacted: Consumes more CPU/Memory


## Release notes:

Please confirm whether to be reflected in release notes and how to describe:
> ex. Fixed the bug .....


Migrated from vesoft-inc#4941

Co-authored-by: codesigner <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@CPWstatic @whitewum @jude-zhu