Sorry, looks like you sent this earlier and I missed it.
A couple of things. One, write_id is per transaction per table. So for
table T, all rows written in w1 will have the same write_id, though they
will each have their own monotonically increasing row_ids. Row_ids are
scoped by a write_id,
Is the following scenario supported?
*timestamp:* t1 < t2 < t3 < t4 < t5 < t6
*w1 -* transaction which updates subset of rows in table T {start_time: t1,
end_time: t5}
*w2 -* transaction which updates subset of rows in table T {start_time: t2,
end_time: t3}
*r1 - *job which reads rows from table
