Yes. I was thinking it would dovetail nicely with a pure text search
service - give a token, receive a Property, then traverse back to the
Element.
g.call("searchService").with("search", "foo") /* returns Properties */
.element() /* traverse to Element */
On Thu, Feb 24, 2022 at 8:23 AM Kelvin Lawrence <[email protected]>
wrote:
> This makes sense I think. Will it be that common for such a service to
> return properties rather than the vertex containing the properties? I
> suppose you are thinking of a case where I do not know the key name and
> just search on values?
>
> Kelvin On Thursday, February 24, 2022, 08:55:12 AM CST, Mike Personick
> <[email protected]> wrote:
>
> I would like to add an ElementStep and corresponding .element() operator.
>
> There is currently no way to traverse from a Property to its Element in
> Gremlin.
>
> Example use case for this would be service calls that return properties
> (e.g. full-text search), which could then be traversed to their owning
> element. I am sure there are others.
>
> I will assume a lazy consensus and proceed with this change if there are no
> objections in the next 72 hours.
>
> Here is the JIRA:
> https://issues.apache.org/jira/browse/TINKERPOP-2713
>
> Thanks,
> MIke
>
