[ 
https://issues.apache.org/jira/browse/TINKERPOP-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946228#comment-17946228
 ] 

ASF GitHub Bot commented on TINKERPOP-3147:
-------------------------------------------

Cole-Greer commented on PR #3096:
URL: https://github.com/apache/tinkerpop/pull/3096#issuecomment-2819510864

   Note: This change should be reflected user upgrade docs. There are quite a 
few of these by-modulating changes going into 3.8 right now, perhaps they 
should all be consolidated into a single upgrade docs entry once all of that 
work is complete.




> Prevent aggregate step from having multiple by modulators
> ---------------------------------------------------------
>
>                 Key: TINKERPOP-3147
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3147
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.7.3
>            Reporter: Andrea C
>            Priority: Minor
>
> Aggregate step will ignore previous by modulators if multiple are specified, 
> which can be misleading to the user. Instead, similar to 
> https://issues.apache.org/jira/browse/TINKERPOP-3121 multiple by modulators 
> should be prevented with aggregate.
> {code:java}
> gremlin> g.V().aggregate('x').by('name').cap('x')
> ==>[marko,vadas,lop,josh,ripple,peter]
> gremlin> g.V().aggregate('x').by('name').by('age').cap('x')
> ==>[29,27,32,35] {code}
>  
> Note that `store` step is an alias to `aggregate` and should also be 
> prevented from having multiple by modulators.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to