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

The newest scan operation has inconsistent behavior for vertex and edge #3445

Open
Nicole00 opened this issue Dec 10, 2021 · 3 comments
Open

The newest scan operation has inconsistent behavior for vertex and edge #3445

Nicole00 opened this issue Dec 10, 2021 · 3 comments

Comments

@Nicole00
Copy link
Contributor

  1. When scan vertex, the result will return the vertex id (_vid) by default.
  2. When scan edge, the result will not return the edge id(_src,_dst,_rank) by default.
@Shylock-Hg
Copy link
Contributor

The is mainly to keep same return format with GetProp RPC call.

@Nicole00
Copy link
Contributor Author

Nicole00 commented Dec 10, 2021 •
edited
Loading

The is mainly to keep same return format with GetProp RPC call.

can you explain it in detail? how getPorp affects the scan's inconsistent behavior. And why don't unify the behaviors for vertex and edge in getProp and scan

@Shylock-Hg
Copy link
Contributor

The is mainly to keep same return format with GetProp RPC call.

can you explain it in detail? how getPorp affects the scan's inconsistent behavior. And why don't unify the behaviors for vertex and edge in getProp and scan

Just for unify behaviors.

@jamieliu1023 jamieliu1023 mentioned this issue Dec 11, 2021
Closed
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
2 participants
@Nicole00 @Shylock-Hg