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 2016/01/13 18:31:39 UTC

[jira] [Updated] (TINKERPOP-570) [Proposal] Provide support for OLAP to OLTP to OLAP to OLTP

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

Marko A. Rodriguez updated TINKERPOP-570:
-----------------------------------------
    Fix Version/s: 3.2.0-incubating

> [Proposal] Provide support for OLAP to OLTP to OLAP to OLTP
> -----------------------------------------------------------
>
>                 Key: TINKERPOP-570
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-570
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.2-incubating
>            Reporter: Marko A. Rodriguez
>             Fix For: 3.2.0-incubating
>
>
> I'm trying to figure out how we can, within a "single traversal", move between OLAP and OLTP at different sections of the traversal. E.g.
> {code}
> [g.V.out.has('age',lt,25)]OLAP[out('parent').out('workPlace')]OLTP[out('coworkers').age.groupCount]OLAP
> {code}
> Going from OLAP to OLTP is easy. We have solved that already as OLAP queries return a {{Traversal<S,E>}} and thus, can be further processed in OLTP. But what about going from OLTP back into OLAP? We need to be able to stream the OLTP results back into traversers on the vertices of the graph -- TinkerGraph (easy), Hadoop (dynamic editing of the disk format!? crazy) .. is there a general pattern that works for all graphs? Finally, what about when the objects are NOT vertices/edges/etc. See the next issue.
> [~mbroecheler]



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