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

Add load graph processor in storage #4535

Closed
wenhaocs opened this issue Aug 17, 2022 · 1 comment
Closed

Add load graph processor in storage #4535

wenhaocs opened this issue Aug 17, 2022 · 1 comment
Assignees

Comments

@wenhaocs
Copy link
Contributor

wenhaocs commented Aug 17, 2022

Like ScanVertices and ScanEdges processors, load the whole graph with customized input and output.

@wenhaocs
Copy link
Contributor Author

wenhaocs commented Aug 17, 2022

The input of ScanVertices are interested TagID and property fields. Previously, we thought the Subgraph matching algo only matches labels. But after further analyzing the common graphs used in subgraph matching, what they match are exactly properties, not labels. Therefore, we can reuse ScanVertices and ScanEdges, and set TagID and EdgeType to some default value. When importing graphs into Nebula, we should also assign one and exactly one Tag or EdgeType.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants