We were using a very old version of Tinkerpop (pre Apache) and it contained
some LGPL files. I assume that upgrading to the Apache version will fix
the LGPL dependency issues that that we are having with the pre Apache
version of TInkerpop.
All of the "keep the schema graph in memory to be used by the inference"
logic is actually fully contained in rya.sail. rya.sail does not reference
Most of tinkerpop.rya is commented out. After looking at the code, I'm
guessing that it was meant to be a "rya backed" tinkerpop layer. While
this is a neat idea, I think that it would be easier to start from scratch
with a Java implementation (rather than groovy) that utilized Apache
On Thu, Oct 13, 2016 at 11:45 AM Adina Crainiceanu <ad...@usna.edu> wrote:
> I'll try to look myself at this over the weekend, but I'm surprised by both
> issues and maybe someone here knows the answers.
> What was the functionality provided by tinkerpop.rya and how come that it
> is not used? I thought it was used to keep the schema graph in memory to be
> used by the inference implementation.
> Are we using an old version of tinkerpop, or why does it bring in LGPL
> dependencies - Apache TinkerPop is a top-level Apache project.
> On Thu, Oct 13, 2016 at 10:38 AM, Aaron Mihalik (JIRA) <j...@apache.org>
> > Aaron Mihalik created RYA-202:
> > ---------------------------------
> > Summary: Remove tinkerpop.rya
> > Key: RYA-202
> > URL: https://issues.apache.org/jira/browse/RYA-202
> > Project: Rya
> > Issue Type: Task
> > Reporter: Aaron Mihalik
> > Assignee: Aaron Mihalik
> > Priority: Blocker
> > tinkerpop.rya is not used and brings in LGPL classes hep/aida from
> > com.tinkerpop.blueprints:blueprints-core:jar
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> Dr. Adina Crainiceanu
> Associate Professor, Computer Science Department
> United States Naval Academy
> 410-293-6822 <(410)%20293-6822>