Spark.Store Transaction Commit Fails Leaving Resource in 'queued' status

[geronimovillarreal]

When creating, updating or deleting a Resource document, the result of commiting the transaction is not evaluated for failure. When the sweep() function is called to move the Resource document from 'queued' to 'current' the collection save result is not evaluated. When this fails no exception is raised and the transaction is not rolled back leaving the Resource document in the state of 'queued'.

Proposed fix is to evaluate the result of Transaction.cs line 144 to ensure the Update was successful and the documents affected is equal to 1. If this evaluation fails, the sweep() mehod will throw an exception with the details of the failure so that the transaction fails and the Rollback() method is called.

[kennethmyhra]

Closing this, these methods are no longer used