Hello Luigi or Luca, I have a question regarding the new Batch Insert class. I have a database that contains 744,496 rows which are loaded as Vertices and 6,445,621 rows which are loaded as Edges. I am using the new OGraphBatchInsert. I am following the procedure described in the Java comments: create edges first and then set Vertix properties. The createEdge() API requires two Long ids for Vertices. Today, I have an incremental counter that I use to generate these Ids. Then, I use the same ids in the set Vertix properties operation.
Questions: Does it matter how large these generated Ids get? Should these ids be used in the same sequential order after creating them for the createEdge and then in the same order for the setVertix properties. Creating Edges is very fast for this size of the graph but setting Vertix properties is slow. Would you know why? Could this be related to the sorting order of the Vertex Ids between createEdge calls and set Vertix properties? I am not sure why set Vertix properties is so slower. I am not setting large properties. I only have 4 properties to set. Thank you for help Emin -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
