Yep, that’s the problem! Thanks Jeff (and Alex Petrov for fixing it).
- Max
> On Sep 13, 2018, at 1:24 pm, Jeff Jirsa wrote:
>
> CASSANDA-13004 (fixed in recent 3.0 and 3.11 builds)
-
To unsubscribe, e-mail: user-unsubscr...@
CASSANDA-13004 (fixed in recent 3.0 and 3.11 builds)
On Thu, Sep 13, 2018 at 1:12 PM Max C. wrote:
> I ran “alter table” today to add the “task_output_capture_state” column
> (see below), and we found a few rows inserted around the time of the ALTER
> TABLE did not contain the same values when
Correction — we’re running C* 3.0.8. DataStax Python driver 3.4.1.
> On Sep 13, 2018, at 1:11 pm, Max C. wrote:
>
> I ran “alter table” today to add the “task_output_capture_state” column (see
> below), and we found a few rows inserted around the time of the ALTER TABLE
> did not contain the
I ran “alter table” today to add the “task_output_capture_state” column (see
below), and we found a few rows inserted around the time of the ALTER TABLE did
not contain the same values when selected as when they were inserted.
When the row was selected, what we saw was:
- test_id —> OK (same as
