You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (Jira)" <ji...@apache.org> on 2019/09/05 16:37:00 UTC
[jira] [Updated] (TINKERPOP-1643) Something's broke in OLAP
[ https://issues.apache.org/jira/browse/TINKERPOP-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette updated TINKERPOP-1643:
----------------------------------------
Description:
I don't know what it's related to, hence the open title on this ticket.
*Base Query (all good)*:
{noformat}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v")
==>v[1]
==>v[2]
==>v[3]
==>v[4]
==>v[5]
==>v[6]
==>[v[1],v[4]]
==>[v[4],v[5]]
==>[v[3],v[6]]
==>[v[2],v[1]]
==>[v[1],v[2]]
==>[v[1],v[3]]
{noformat}
As of 3.3.9-SNAPSHOT the above looks like this now:
{code}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v")
==>v[1]
==>v[3]
==>v[2]
==>v[4]
==>v[1]
==>v[6]
==>v[5]
==>v[2]
==>v[3]
==>v[4]
==>v[5]
==>v[6]
{code}
*Issues*:
{noformat}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v").count()
==>6
==>6
{noformat}
{noformat}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v").order().by(count(local))
==>v[1]
==>v[1]
==>v[2]
==>v[2]
==>v[3]
==>v[3]
==>v[4]
==>v[4]
==>v[5]
==>v[5]
==>v[6]
==>v[6]
==>[v[1],v[4]]
==>[v[4],v[5]]
==>[v[3],v[6]]
==>[v[2],v[1]]
==>[v[1],v[2]]
==>[v[1],v[3]]
{noformat}
I'm going to create a dev branch and test cases tomorrow.
was:
I don't know what it's related to, hence the open title on this ticket.
*Base Query (all good)*:
{noformat}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v")
==>v[1]
==>v[2]
==>v[3]
==>v[4]
==>v[5]
==>v[6]
==>[v[1],v[4]]
==>[v[4],v[5]]
==>[v[3],v[6]]
==>[v[2],v[1]]
==>[v[1],v[2]]
==>[v[1],v[3]]
{noformat}
*Issues*:
{noformat}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v").count()
==>6
==>6
{noformat}
{noformat}
gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v").order().by(count(local))
==>v[1]
==>v[1]
==>v[2]
==>v[2]
==>v[3]
==>v[3]
==>v[4]
==>v[4]
==>v[5]
==>v[5]
==>v[6]
==>v[6]
==>[v[1],v[4]]
==>[v[4],v[5]]
==>[v[3],v[6]]
==>[v[2],v[1]]
==>[v[1],v[2]]
==>[v[1],v[3]]
{noformat}
I'm going to create a dev branch and test cases tomorrow.
> Something's broke in OLAP
> -------------------------
>
> Key: TINKERPOP-1643
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1643
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.3.0, 3.2.5
> Reporter: Daniel Kuppitz
> Assignee: stephen mallette
> Priority: Major
>
> I don't know what it's related to, hence the open title on this ticket.
> *Base Query (all good)*:
> {noformat}
> gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v")
> ==>v[1]
> ==>v[2]
> ==>v[3]
> ==>v[4]
> ==>v[5]
> ==>v[6]
> ==>[v[1],v[4]]
> ==>[v[4],v[5]]
> ==>[v[3],v[6]]
> ==>[v[2],v[1]]
> ==>[v[1],v[2]]
> ==>[v[1],v[3]]
> {noformat}
> As of 3.3.9-SNAPSHOT the above looks like this now:
> {code}
> gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v")
> ==>v[1]
> ==>v[3]
> ==>v[2]
> ==>v[4]
> ==>v[1]
> ==>v[6]
> ==>v[5]
> ==>v[2]
> ==>v[3]
> ==>v[4]
> ==>v[5]
> ==>v[6]
> {code}
> *Issues*:
> {noformat}
> gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v").count()
> ==>6
> ==>6
> {noformat}
> {noformat}
> gremlin> g.V().as("v").emit().repeat(both().as("v").dedup()).select("v").order().by(count(local))
> ==>v[1]
> ==>v[1]
> ==>v[2]
> ==>v[2]
> ==>v[3]
> ==>v[3]
> ==>v[4]
> ==>v[4]
> ==>v[5]
> ==>v[5]
> ==>v[6]
> ==>v[6]
> ==>[v[1],v[4]]
> ==>[v[4],v[5]]
> ==>[v[3],v[6]]
> ==>[v[2],v[1]]
> ==>[v[1],v[2]]
> ==>[v[1],v[3]]
> {noformat}
> I'm going to create a dev branch and test cases tomorrow.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)