I am still testing... however when I create the connection with autoStartTx
= false. It seems to update the index correctly.
OrientGraph graph = new
OrientGraph("plocal:/oriendb/databases/IndexTestDB", *false*);
*blueprints.orientdb.autoStartTx Auto start a transaction as soon the graph
is changed by adding/remote vertices and edges and properties true*
On Thursday, April 23, 2015 at 3:45:07 PM UTC-5, Abraham Farris wrote:
>
>
> It seems that automatic indexing behaves differently between a tx commit
> and an nonTx commit. I have included my test.
>
> In the results.png "abraham" is created with graph transaction. The
> "lincoln" entry is created a with a graph non-transaction.
>
> For some reason the index never automatically updates in a transaction
> commit, it only on updates during a non-transaction commit.
>
> Any advice would be appreciated. Perhaps this is a setting or I can call
> a method to update the index after the transaction is successful?
>
> Thanks,
>
> Abe
>
--
---
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.
