Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-1128

Change the Gryo serialization for StarGraph (Vertex, Properties, then Edges)

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 3.1.1-incubating
    • None
    • io

    Description

      Right now we serialize first the vertex, then its edges, then its properties. We should do vertex, properties, edges. Why? If we know that the vertex is to be filtered (which is an analysis of its label/id/properties), then we can skip over analyzing its edges. Right now, we may do all this work deserializing edges only to realize that the GraphFilter says that the vertex is filtered. Dah, pointless clock cycles – especially when edge sets can be massive.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. TINKERPOP-1122 StarGraph has a Long nextId. That is pointless and a waste of 64-bits.

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. TINKERPOP-1343 A more efficient StarGraph serialization representation.

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. TINKERPOP-1461 StarGraph has bad detach/attach logic for properties.

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              okram Marko A. Rodriguez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: