Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Support Gremlin multi-label vertexes #538

Open
michaelnchin opened this issue Nov 10, 2023 · 0 comments
Open

Support Gremlin multi-label vertexes #538

michaelnchin opened this issue Nov 10, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@michaelnchin
Copy link
Member

Community Note

  • Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Is your feature request related to a problem? Please describe.

Per their docs, Neptune supports use of multiple labels for a single vertex in Gremlin data, via the :: syntax.

The Gremlin graph visualizer does not currently recognize or provide any special processing for multi-labels included in query results.

Describe the solution you'd like

The Gremlin visualizer options --display-property and --group-by-property should be able to factor in multi-label vertexes when matching on a single label value.

For example, if a %%gremlin query returns the multi-label vertex:

{<T.id: 1>: '0', <T.label: 4>: 'Label1::Label2::Label3', 'name': 'a_vertex'}

Users should be able to pass the following to --display-property:

my_node_labels = ‘{“Label1”:“name”}’`

And get "a_vertex" as the displayed value on the same vertex in the visualized graph.

@michaelnchin michaelnchin added the enhancement New feature or request label Nov 10, 2023
@michaelnchin michaelnchin moved this to Low priority in Graph Notebook Planning Jun 12, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
Status: Low priority
Development

No branches or pull requests

1 participant