Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-7274

[RESP] TX allows to continue upon error when queuning commands

XMLWordPrintable

      While Redis does not allow WATCH within the TX but still proceeds with it's execution (JDG-7273), it's expected that the command resulting in error will halt the transaction:

      Infinispan:

      127.0.0.1:11222> multi
OK
127.0.0.1:11222(TX)> set foo fooer
QUEUED
127.0.0.1:11222(TX)> non-exising-command
(error) ERR unknown command
127.0.0.1:11222(TX)> set bar baer
QUEUED
127.0.0.1:11222(TX)> exec
1) OK
2) OK
127.0.0.1:11222> exists foo
(integer) 1

      Redis:

      127.0.0.1:6379> multi
OK
127.0.0.1:6379(TX)> set foo fooer
QUEUED
127.0.0.1:6379(TX)> non-existing-command
(error) ERR unknown command 'non-existing-command', with args beginning with: 
127.0.0.1:6379(TX)> set bar baer
QUEUED
127.0.0.1:6379(TX)> exec
(error) EXECABORT Transaction discarded because of previous errors.
127.0.0.1:6379> exists foo
(integer) 0

              rh-ee-jbolina Jose Bolina
              rhn-support-pdrobek Pavel Drobek
              Pavel Drobek Pavel Drobek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: