In database systems, atomicity is one of the ACID (Atomicity, Consistency, Isolation, Durability) transaction properties. An atomic transaction is a series of database operations that cannot be divided or reduced such that one of the following happens:
all of the transaction occurs
none of the transaction occurs
This ensures that databases or tables will not be partially updated in certain cases which might create problems. This also means that the progress of the transaction cannot be observed by another database client. It shows either as not occurred or as completed.
In Treasure Data, the four supported modes below are atomic because they use a temporary table to store the incoming data before attempting to modify the destination table: