Commit does not rollback when bad data causes RF2 import to fail

[kaicode]

RF2 imports can fail. For example if there are badly formatted or duplicate rows.

In these cases the Snowstorm commit fails but the commit does not automatically rollback so the partially imported content is left on the branch in an uncompleted commit. The branch is left locked. The branch will not unlock because of the partially committed content.

There is a workaround to resolve this situation using Elasticsearch queries but this situation is highly undesirable!