[jira] [Closed] (TINKERPOP3-533) Synthetic properties

["Marko A. Rodriguez (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP3-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko A. Rodriguez closed TINKERPOP3-533.
-----------------------------------------
    Resolution: Won't Fix
      Assignee: Marko A. Rodriguez

The {{GraphTraversal}} DSL will be what it is. If people want to have their own fluent methods, this is where they create their own {{MyTraversal}} DSL. We will see DSL techniques later in the 3.x series.

> Synthetic properties
> --------------------
>
>                 Key: TINKERPOP3-533
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-533
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.0-incubating
>            Reporter: Nik Everett
>            Assignee: Marko A. Rodriguez
>
> It'd be nice to be able to make synthetic properties that only exist for reading.  Like
> {code:groovy}
> def labelDef = {v-> v.property('labelEn').orElseGet{v.property('labelDe').orElseGet{v.property('somethingElse')}}}
> g.V().synthetic('label', labelDef).has('foo', 'start').as('start').out().as('finish').select().by('label')
> {code}
> or
> {code:groovy}
> g.V().synthetic('label', labelDef).has('label', 'bar')
> {code}
> Obviously the last one wouldn't be indexed and it _would_ be convenient.
> I like having this configured on the Traversal level because then it could be reset at traversal time.  In this case the use case would be for a user to configure a different label fallback strategy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)