Abstract: Methods, systems, and computer program products are described herein for updating big data tables using snapshot isolation. The tables may store data (e.g., as data objects) collected from different users. The tables are stored in a first data store. The data's metadata is stored in a second data store. The metadata comprises version numbers for the objects that correspond to a consistent version thereof. When an update process for the table is initiated, a coordinator locks the metadata, and. the objects are updated. If the update to the objects is successful, the coordinator commits the updates and obtains the new version numbers of the objects. If all the commits are successful, the coordinator atomically updates the metadata with the new version numbers and releases the lock. However, if a commit to an object is unsuccessful, a subsequent process rolls back the committed objects to the version numbers specified by the metadata.

Abstract: Methods, systems, and computer program products are described herein for updating big data tables using snapshot isolation. The tables may store data (e.g., as data objects) collected from different users. The tables are stored in a first data store. The data's metadata is stored in a second data store. The metadata comprises version numbers for the objects that correspond to a consistent version thereof. When an update process for the table is initiated, a coordinator locks the metadata, and. the objects are updated. If the update to the objects is successful, the coordinator commits the updates and obtains the new version numbers of the objects. If all the commits are successful, the coordinator atomically updates the metadata with the new version numbers and releases the lock. However, if a commit to an object is unsuccessful, a subsequent process rolls back the committed objects to the version numbers specified by the metadata.