Hi Macheal, The results should be the same. If you want to know the sub classes of V, you can use the Java Schema API:
OClass v = graph.getVertexBaseType(); // GET DIRECT BASE CLASSES Collection<OClass> baseClasses v.getSubclasses(); // GET ALL BASE CLASSES Collection<OClass> baseClasses v.getAllSubclasses(); Lvc@ On 25 June 2015 at 02:11, Michael Pollmeier <[email protected]> wrote: > Hi Luca, > > Labels are now implemented as orient classes (Vertex only for now). They > work fine for a `remote:localhost/mygraph` connection, but something is > different for a `memory:mygraph` connection. > When I create vertices with different labels and then list all vertices > (polymorphic = true) it should return all vertices as they all extend V. > That works fine using a remote instance, but not a memory instance - it > only returns the vertices with class `V`. > > Do you have any hints on how to debug this? I am able to execute > Orient-SQL queries a la `select from V` but I if I try something like `list > classes`, Orient throws the following: `OCommandExecutorNotFoundException: > Cannot find a command executor for the command request: sql.list classes` > > Can you have a look at the implementation and see if there's anything > obvious I'm doing wrong? > > https://github.com/mpollmeier/orientdb-gremlin/tree/master/src/main/java/org/apache/tinkerpop/gremlin/orientdb/structure > > Cheers > Michael > > > On 06/19/2015 09:16 PM, Luca Garulli wrote: > >> Michael, >> Thanks for this job. About 1) in TP2.x we used OrientDB classes for >> labels. >> I think we can maintain this coupling to have benefit about class schema >> and class partitioning. So each label is a class. vertex label are classes >> that extends "V" (the base vertex class), while edge classes should extend >> "E". >> >> On 19 June 2015 at 05:39, Michael Pollmeier <[email protected] >> > >> wrote: >> >> @Luca: you can disregard question 2 from below. >>> VertexProperties can now be set and looked up fine. >>> >>> >>> On 06/18/2015 03:53 PM, Michael Pollmeier wrote: >>> >>> Thanks guys. I moved it to a separate repo, feel free to contribute or >>>> steal from it: https://github.com/mpollmeier/orientdb-gremlin/ >>>> >>>> @Luca: a couple of questions for you: >>>> 1) Now that both vertices and edges have labels, how would you model >>>> them? Use a system column similar to @RID and @CLASS, e.g. @LABEL? >>>> >>>> 2) When looking up vertices by their ids, what's the easiest way to use >>>> the right index? Currently I'm scanning all vertices... >>>> >>>> >>>> https://github.com/mpollmeier/orientdb-gremlin/blob/master/src/main/java/org/apache/tinkerpop/gremlin/orientdb/structure/OrientGraph.java#L67 >>>> >>>> >>>> Cheers >>>> Michael >>>> >>>> On 06/17/2015 10:16 PM, Stephen Mallette wrote: >>>> >>>> Very cool, Michael. In answer to your question about where the >>>>> OrientDB >>>>> implementation will live, I think that it will stay with OrientDB. >>>>> >>>>> On Wed, Jun 17, 2015 at 5:20 AM, Luca Garulli <[email protected]> >>>>> wrote: >>>>> >>>>> Hi Michael, >>>>> >>>>>> Thanks for your initiative! >>>>>> >>>>>> I confirm OrientDB will support TP3 in the future. A few months ago, >>>>>> the >>>>>> OrientDB Team decided to postpone the support for TP3 until the it >>>>>> would >>>>>> reach the final status. >>>>>> >>>>>> Since OrientDB Graph API is completely based on TP2.x, it's >>>>>> impossible to >>>>>> replace the API without hurting clients and users. So at the >>>>>> beginning, TP3 >>>>>> (+JDK8) will be a separate module, but it slowly will replace our >>>>>> Graph API >>>>>> ;-) >>>>>> >>>>>> If you Michael and other volunteers want to work on it in the Open >>>>>> Source >>>>>> sake, we could support you guys ;-) >>>>>> >>>>>> >>>>>> >>>>>> On 17 June 2015 at 08:13, pieter-gmail <[email protected]> >>>>>> wrote: >>>>>> >>>>>> +1 >>>>>> >>>>>>> >>>>>>> On 17/06/2015 08:11, Michael Pollmeier wrote: >>>>>>> >>>>>>> I just had a first shot at implementing an OrientGraph for TP3. So >>>>>>>> far >>>>>>>> it can only list all vertices and a vertex can only return it's ID >>>>>>>> and >>>>>>>> all of it's properties, but it's a start ;) >>>>>>>> >>>>>>>> My goal is to create a proof of concept rather than a full >>>>>>>> implementation, i.e. Luca or some other Orient expert will need to >>>>>>>> take this over or start from scratch. >>>>>>>> >>>>>>>> Is the intention to have the orient driver in the TP3 codebase or >>>>>>>> will >>>>>>>> it replace the TP2 driver in the orientdb codebase? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> https://github.com/mpollmeier/tinkerpop3/tree/MP1-SNAPSHOT/orientdb-gremlin/src/main/java/org/apache/tinkerpop/gremlin/orientdb/structure >>>>>> >>>>>> >>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>
