Interface TransactionBase

    • Method Detail

      • delete

        void delete​(Bytes row,
                    Column col)
        Deletes the value at the given row and Column
      • setWeakNotification

        void setWeakNotification​(Bytes row,
                                 Column col)
        Sets a weak notification at the given row and Column
      • withReadLock

        default SnapshotBase withReadLock()
        Normally when a Fluo transaction reads data and does not write to it, it will not collide with other transactions making concurrent writes. When this method is called, all reads will acquire a read lock. These read locks cause collisions with transactions doing concurrent writes. However, multiple transactions can get concurrent read locks on the same row+col without colliding.

        Scanning with read locks is not supported. Attempting to call withReadLock().scanner() will throw an UnsupportedOperationException. This is because there are an infinite amount of keys within a range and read locks can not be obtained on them all.

        A transaction that only acquires read locks will do nothing at commit time. In this case no read locks are actually written and no collisions will ever occur.

        Since:
        1.2.0