What I'm trying to point out is that while TinkerPop today represents, as
Marko mentioned, the bare minimum API to get things working, it would be
nice if in the future TinkerPop as an API for graph databases could include
common performance-related features. If the TinkerPop API supported
indexes,
On Fri, Jul 22, 2016 at 7:39 PM, Jonathan Ellithorpe
wrote:
> Sorry for the delay here, been away for a while...
>
> Thanks for clarifying things. That makes sense... it's a bit different from
> the MySQL storage engine model, where one simply implements the API for a
> new storage engine,
Check.
Sorry for the delay here, been away for a while...
Thanks for clarifying things. That makes sense... it's a bit different from
the MySQL storage engine model, where one simply implements the API for a
new storage engine, plugs it in, and the "top-half" doesn't change (e.g.
the query planner / stor
Hi,
> 4) Some important features are absent from the API. For social networks,
>> it's often very important to be able to keep edges ordered by a particular
>> property key (say "creationDate") and read edges in a particular
>> time-window (say between now and 7 days ago) or with a particular limi
Jonathan, thanks for the detailed feedback.
In general, though, I felt that a
> developer walk-though-guide of the API would have been very helpful.
>
It would be nice if our Provider Documentation read more that way:
http://tinkerpop.apache.org/docs/3.2.0-incubating/dev/provider/
It would be g
Hi all, I caught sight of this thread a while back but haven't had much
time for e-mail...
As an implementer, experientially I found implementing the API to be rather
difficult / unclear. Below is a random list of some of the gripes that I
had. Dunno if other implementers have the same gripes but
> People who just click links and copy paste code snippets w/o being aware
of 2.x/3.x sort of stuff
that is a fascinating phenomena, isn't it.
On Thu, May 26, 2016 at 7:00 AM, Marko Rodriguez
wrote:
> > You know what else i just noticed?
> >
> > http://gremlin.tinkerpop.com
> > http://rexster.t
> You know what else i just noticed?
>
> http://gremlin.tinkerpop.com
> http://rexster.tinkerpop.com
> and so on
>
> all still point to the old wikis - should we consider changing those to
> have them all just go to the 3.x home page?
I believe there are more people on 2.x than there are on
I swear that one of the worst offenders for old links is stackoverflow. I
get upvotes all the time on ancient TP2 answers that link directly into the
old github wikis. You would think that folks would eventually notice our
link to redirect to TinkerPop 3.x but who knows. Maybe we could write a
scri
> but maybe perhaps Stephen would like to get a talk like that at Cassandra
Summit?
hehe - i'm sure you could have found a way to make that topic interesting.
i'm not so sure i could. :)
> Psssht, the original Uni_pop _has Tinkerpop support, and a better unicorn
logo...
ha!
> Seriously though,
More stuff ---
One thing I think that we really need to drive home to providers is
TraversalStrategies. That should be a blog post too. I've talked to two graph
databases providers recently and both were concerned about performance through
the TinkerPop API. They didn't know they could write pr
Psssht, the original Uni_pop _has Tinkerpop support, and a better unicorn
logo...
Seriously though, for wider Tinkerpop adoption it would be cool to have a
general "Provider Template" along with the tutorial/blogpost :
* Default `structure` implementation, with /*IMPLEMENT READ/WRITE/ETC
Hi,
> I've been tinkering recently in this space, more specifically to better
> understand the gremlin-test suite in general. A blog post sounds like a
> good idea. I can take a stab at it.
Cool.
>> Maybe working on referencing these pages via perhaps a blog post from
>> someone would be cool. S
Maybe working on referencing these pages via perhaps a blog post from
someone would be cool. Something along the lines of "Creating a graph db
with Tinkerpop" or some other variation that may get good hit results in a
google search.
On Wed, May 25, 2016 at 10:06 AM, Stephen Mallette
wrote:
> We'
Agreed. A big on-going problem TinkerPop has is that people invariably
stumble upon TinkerPop 2 and Blueprints/Pipes. If they find TP2, maybe they
presume it is dead, so they roll their own.
I've been tinkering recently in this space, more specifically to better
understand the gremlin-test suite i
We've seen a lot of new graphs come out that don't do TinkerPop from the
start. Perhaps they make a conscious decision not to - i dunno. I just
wonder if part of the problem is the provider docs for doing an
implementation:
http://tinkerpop.apache.org/docs/3.2.0-incubating/dev/provider/
are they
Hi,
See https://github.com/haifengl/unicorn
They say they support a "Gremlin-like API." It would be really cool if they
just implemented TinkerPop's Graph API. Perhaps someone feels like creating a
ticket at their main repo explaining how to go about supporting TinkerPop? Or,
even bett
17 matches
Mail list logo
