[jira] [Closed] (TINKERPOP-1244) PropertyMapStep should allow by modulation.

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

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

Marko A. Rodriguez closed TINKERPOP-1244.
-----------------------------------------
    Resolution: Won't Fix
      Assignee: Marko A. Rodriguez

This is just pointless additions to the language. Going to close with a "won't fix." If someone has an argument for doing it, please re-open.

The example I provided in the ticket was:

{code}
g.V().propertyMap().by(properties().count())
{code}

...simply do:

{code}
g.V().map(properties().group().by(key()).by(count()))
{code}



> PropertyMapStep should allow by modulation.
> -------------------------------------------
>
>                 Key: TINKERPOP-1244
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1244
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.1-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>
> We have {{ProjectStep}} which allows to project traversals off the current object. {{PropertyMapStep}} should extend {{ProjectStep}} and then it will have {{by()}}-modulation capabilities. Why is this good?
> {code}
> // for each property, how many meta properties does it have?
> g.V().propertyMap().by(properties().count())
> {code}
> A minor thing that gives us a bit more expressivity and allows {{ProjectStep}} to take its rightful place as a more fundamental step like {{SelectStep}}.



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