a quick 2 cents....i took a stab at this a while back because there was some reason why i thought it would be useful in the test suite. my approach ended up looking like it was going to go the way of indices (which we all know has been relegated to the vendor's API and something outside of TinkerPop). I have some interest in seeing it part of the API, but not if the solution is going to
1. bring an overly complex API to TinkerPop which makes TP3 harder to implement and hard to write tests for in the test suite and 2. not provide any real features to users (e.g.. createKeyIndex(String, Class) from TP2 in relation to Titan). I think it would be nice to see some other vendor implementations that had a Schema API before we consider adding that kind of thing. afaik, titan is the only graphdb that has such a thing. On Wed, May 20, 2015 at 2:33 PM, Dylan Millikin <[email protected]> wrote: > I haven't had a chance to play around with TP3 much yet but the idea of > having the schema available is quite interesting. Especially if this could > keep track of basic index information. In TP2 getting indices per label > etc. was somewhat tedious and quite vendor specific. > Maybe something simple can be done on that end? > > On Wed, May 20, 2015 at 1:52 PM, pieter-gmail <[email protected]> > wrote: > > > Hi, > > > > This is to hear what the community thinks about tinkerpop auto capturing > > schema information. > > > > Since labels, any tinkerpop graph has a schema and seeing that tinkerpop > > captures every vertex and edge with its label it could transparently > > maintain this in the db itself. > > > > It should add little to no overhead to capturing data as schemas change > > seldom and are small compared to the actual data. > > > > There are may use cases for having the schema available as part of the > > regular graph. > > > > * Natural place to attach further (non tinkerpop) info like acl, audit > > rules, multiplicities, navigability > > * Might enable code insight for gremlin. > > * Store performance/analytic result. > > * Easy for new users to understand any graph's schema > > * Might facilitate gremlin optimization > > ... > > > > I understand that may implementations have their own peculiar schema > > requirements. However my idea is not to walk a path outside of > tinkerpop's > > own semantics. > > > > Besides all that there is something sweet about a graph > > containing/managing its own meta data. > > > > Thanks > > Pieter > > >
