You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/09/02 23:59:45 UTC

[jira] [Created] (TINKERPOP3-831) How should OLAP treat Collection objects? No contract is specified.

Marko A. Rodriguez created TINKERPOP3-831:
---------------------------------------------

             Summary: How should OLAP treat Collection<Element> objects? No contract is specified.
                 Key: TINKERPOP3-831
                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-831
             Project: TinkerPop 3
          Issue Type: Bug
          Components: process
            Reporter: Marko A. Rodriguez
            Assignee: Marko A. Rodriguez
             Fix For: 3.1.0-incubating


Assume the following OLAP query:

{code}
g.V.group.by(label).by().by(order(local).by('name'))
{code}

The {{Map<String,List<Vertex>>}} that is processed by {{GroupMapReduce}} doesn't have "real vertices." For TinkerGraph/Spark/Giraph, we use {{DetachedVertices}}. However, we don't have a specification for forcing this on vendors. ........ We need a contract so its not "who knows?! -- pura vida -- namaste -- comme ci, comme ça"



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