[Rexster] OrientDB

[stephen mallette]

At least two issues were noted around OrientDB operations with Rexster in the last month or so.  Both issues had to do with inconsistent results from Rexster.  With a more than fair amount of help from Luca, we've been able to resolve the issues (one was fixed by a one-line global configuration adjustment to how Rexster configured the OrientDB connection and the other was actually fixed through a problem with the Blueprints implementation).  The tests scenarios that I was using to replicate the fail sequences no longer show a problem so it looks as though the issues have been resolved.

I think Marko deployed Blueprints to the snapshot repo yesterday so a fresh build of Rexster should resolve these issues.

Best regards,

Stephen

[Marko Rodriguez]

Hi,

I think Marko deployed Blueprints to the snapshot repo yesterday so a fresh build of Rexster should resolve these issues.

I have not, but I have some work about to be deployed so I will ping everyone when its ready.

Thanks Stephen,

Marko.

http://markorodriguez.com

[Luca Garulli]

Hi,

you should see a pull request from me some days ago ;-)

Lvc@

[Luca Garulli]

Thank you Stephen,

now the OrientDB Blueprints implementation is more robust and stable in Multi-Thread contexts.

Lvc@