See [here](http://docs.neo4j.org/chunked/milestone/rest-api-unique-indexes.html#rest-api-get-or-create-unique-node-create) - if this is set to true, and you encounter a conflict, the old object (with which the one you are saving conflicted) is returned, rather than your original object. False is the default on `setUniqueKey` - and it would probably make sense here (meaning the save would fail if there was a key conflict). So you could just omit that argument altogether