Hi All I am having a weird problem while creating vertex and edges. Here is what I am trying to do
I have a Group class (a vertex) and a Member (again vertex) class. I create a Group class with its properties and then create Member vertex one by one. After Member vertex created, I add a edge to Group vertex to Member vertex. I have 300 members per group. So each Member vertex creation is associated with an edge creation. But after adding 200 Member vertex I gets this warning WARNING: Requested command 'Committing the active transaction to create the new type 'Member' as subclass of 'V'. The transaction will be reopen right after that. To avoid this behavior create the classes outside the transaction' must be executed outside active transaction: the transaction will be committed and reopen right after it. To avoid this behavior execute it outside a transaction I am using transactional OrientGraph object and blueprint APIs. Above operation is done on a single graph connection. However I do in between open new graph and shutdown. This is only for querying. However initial graph remains open till my operation finishes. Funny thing is that I can see , from studio interface, 'uncommitted' Edges piling up on Group vertex. But If I drill down I get an error. I have monitored availability of connection pool it is just using 1 connection. >From that warning I understand that new vertex should be added with new transaction but I did not understand why uncommitted edges appearing in database. Second thing which is more strange why app is hanging midway ie after 200 Member vertex. I am using latest orientdb-community-1.7.8 edition. Any thought? Thanks for uour time/ -- --- 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.
