non-transactional: ignores commits, updates are permanent. no rollback. a cassandra incrementing state would be like this
repeat-transactional: idempotent as long as all batches for a txid are identical
opaque-transactional: the most general kind of state. updates are always done based on the previous version of the value if the current commit = latest stored commit Idempotent even if the batch for a txid can change.
repeat transactional is idempotent for transactional spouts opaque transactional is idempotent for opaque or transactional spouts
Trident should log warnings when state is idempotent but updates will not be idempotent because of spout