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 insert)
- test_instance_group_id —> inserted as UNSET_ID, selected it contained the
same value as test_id
- test_name —> OK (same as insert)
- ti_exec_flow —> inserted as “STD”, selected it contained the same value as
test_name
Does this ring a bell? Is there a JIRA for this (hopefully fixed in a newer
C*)? We’re running 3.0.6. Thanks everyone.
CREATE TABLE mars.test_instances_by_run_submission (
run_submission_id timeuuid,
rs_bucket_num int,
id timeuuid,
active_task_id timeuuid,
active_task_name_path text,
exec_end timestamp,
exec_gpath text,
exec_host_id uuid,
exec_start timestamp,
exec_state text,
exec_subbuild_id timeuuid,
exec_vco text,
fstatus text,
grid_job_id uuid,
legacy_assert boolean,
legacy_core boolean,
source_gpath text,
task_output_capture_state text, # NEW
test_id uuid,
test_instance_group_id uuid,
test_name text,
ti_exec_flow text,
PRIMARY KEY ((run_submission_id, rs_bucket_num), id)
) WITH CLUSTERING ORDER BY (id ASC)
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
