You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Graph Notebook Version (and Graph Database and Version used if applicable)
Is your feature request related to a problem? Please describe.
I'm using my edge labels to identify the type of relationship between two nodes. However, in my application logic, I also store a timestamp of when the data relationship has been updated. I'd like to be able to have a "heatmap-like" visualization where older relationships (and nodes) are slightly discolored / darker / less opaque relative to more freshly updated entities.
Describe the solution you'd like
Ideally, I'd like to be able to set a flag like %%oc -d $display_var -l 50 -g cluster_id -de $edge_display --edge_colorize PROPERTYNAME. ... and then you do the calculation :)
Additional context
Current workaround, run the same query with different properties as the edge labels
The text was updated successfully, but these errors were encountered:
Community Note
Graph Notebook Version (and Graph Database and Version used if applicable)
Is your feature request related to a problem? Please describe.
I'm using my edge labels to identify the type of relationship between two nodes. However, in my application logic, I also store a timestamp of when the data relationship has been updated. I'd like to be able to have a "heatmap-like" visualization where older relationships (and nodes) are slightly discolored / darker / less opaque relative to more freshly updated entities.
Describe the solution you'd like
Ideally, I'd like to be able to set a flag like
%%oc -d $display_var -l 50 -g cluster_id -de $edge_display --edge_colorize PROPERTYNAME
. ... and then you do the calculation :)Additional context
Current workaround, run the same query with different properties as the edge labels
The text was updated successfully, but these errors were encountered: