Feedback after the test with G6VP visualization platform
- Dominant language
- C++
- Stars
- 3.6k
- Forks
- 468
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Here is the feedback after the test of [supported gremlin step](https://graphscope.io/docs/latest/interactive_engine/supported_gremlin_steps) with the [G6VP](https://github.com/antvis/G6VP) visualization platform. I believe some of them may helpful for our GIE engine.
- Query an edge property is not supported yet.
```
g.E().valueMap()
```
- Could the result of `expandPath` operator carry the edge information? It'll be helpful for graph visualization. Thanks for @BingqingLyu, a new option `ALL_E` may be a good solution.
```shell
g.V().both("1..3", "knows").with('RESULT_OPT', 'ALL_E')
```
- Now, the result of `label` operator is a list of `numeric`, which may be confusing for our user.
```
g.V().label()
[1,1,1,2,2,2,2]
```
- The results' order of querying the properties with multiple vertexes is inconsistent with the vertex input. This will cause that we are not able to query the vertex properties in batch
```
g.V(1,2,3).valueMap()
```
/cc @longbinlai
Contributor guide
Research direction
Review the supported Gremlin steps documentation and reproduce the four behaviors using the queries shown: edge-property lookup, expandPath edge information, label output, and multi-vertex property ordering. Done means the agreed behavior is implemented or clarified for G6VP visualization use, with each listed query producing the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100