[
https://issues.apache.org/jira/browse/TINKERPOP-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298213#comment-15298213
]
ASF GitHub Bot commented on TINKERPOP-1307:
-------------------------------------------
Github user okram commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/318#issuecomment-221280324
Did some more benchmarking of `master/` vs. this branch The times are "the
same."
```
// result: {cover=368579, =160968, original=771317}
// old vs. new
// STANDARD
Big Values -- by(songType)
group: 432.720949 vs. 440.4774939999999
group: 428.08102429999997 vs. 438.2646092
Big Keys -- by(name)
group: 426.047715 vs. 392.74015999999995
group: 452.2799462 vs. 405.5412201
// COMPUTER
Big Values -- by(songType)
group: 54.3288408 vs. 61.9877934
group: 90.81696539999999 vs. 84.366255
Big Keys -- by(name)
group: 31.852916 vs. 31.7736176
group: 53.63283839999999 vs. 60.662042799999995
```
> NPE with OLTP nested group() in an OLAP group() traversal
> ---------------------------------------------------------
>
> Key: TINKERPOP-1307
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1307
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.2.0-incubating
> Reporter: Marko A. Rodriguez
>
> {code}
> graph = TinkerGraph.open()
> graph.io(graphml()).readGraph('data/grateful-dead.xml')
> g = graph.traversal().withComputer()
> g.V().hasLabel('song').match(
> __.as('songV').values('name').as('songName'),
> __.as('songV').out('followedBy').as('followedV'),
> __.as('followedV').values('name').as('followedName'),
> __.as('followedV').out('sungBy').as('sungByV'),
> __.as('sungByV').values('name').as('sungBy'),
> __.as('followedV').out('writtenBy').as('writtenByV'),
> __.as('writtenByV').values('name').as('writtenBy')
> ).select('songName','followedName','sungBy','writtenBy').
>
> group().by(select('songName')).by(group().by(select('followedName')).by(select('sungBy').fold()))
> {code}
> The above causes an NPE. I know why -- potentially easy fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
