You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Puja Valiyil (JIRA)" <ji...@apache.org> on 2017/04/13 14:43:41 UTC

[jira] [Resolved] (RYA-230) Revive Blueprints/Tinkerpop support for Rya

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

Puja Valiyil  resolved RYA-230.
-------------------------------
    Resolution: Fixed

> Revive Blueprints/Tinkerpop support for Rya
> -------------------------------------------
>
>                 Key: RYA-230
>                 URL: https://issues.apache.org/jira/browse/RYA-230
>             Project: Rya
>          Issue Type: New Feature
>          Components: clients
>            Reporter: Puja Valiyil 
>            Assignee: Puja Valiyil 
>
> Previously Rya users could use the SAIL Graph provided with Blueprints as an adapter for their graph analytics.  Since this is no longer maintained, we should look at providing tinkerpop/gremlin support specific to Rya.
> Since there are fewer contracts with Gremlin/Tinkerpop compared to Spark/GraphX, we can probably make the adapter dependent on only the core tables.  
> Statement Metadata could be used for applying properties to edges, and a specific triple could be added to specify properties on vertices.  We could also not support properties on vertices, but this seems like a cop out.  Some decisions would have to be made as to how much to initially load versus dynamically query when a user creates a vertice or edge.  We could also look at what other triplestores do to provide properties on vertices/edges.  Stardog might be  good place to start -- they do something with reification.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)