Failed running "dump" timestamp

Im having issues running a dump against a table that as a timestamp field.
The dump is able to dump the schema, but not the data.
$ cockroach dump sos question --dump-mode=both --insecure

Client version: CockroachDB CCL v1.1.6 (darwin amd64, built 2018/03/12 22:33:39, go1.10)

Server version: CockroachDB CCL v2.0.2 (x86_64-unknown-linux-gnu, built 2018/05/21 14:55:20, go1.10)

Cluster ID: d3d5f288-6b63-471e-b3d4-920145366f9f

CREATE TABLE question (
uid INT NOT NULL DEFAULT unique_rowid(),
old_id INTEGER NULL,
path STRING NULL,
title STRING NULL,
test_id INTEGER NULL,
choices JSON NULL,
question_type STRING NULL,
category STRING NULL,
created_on TIMESTAMP NULL,
CONSTRAINT “primary” PRIMARY KEY (uid ASC),
UNIQUE INDEX question_path_key (path ASC),
INDEX ix_question_old_id (old_id ASC),
INDEX ix_question_question_type (question_type ASC),
FAMILY “primary” (uid, old_id, path, title, test_id, choices, question_type, category, created_on)
);
Error: unknown timestamp type: 2018-07-18 17:43:41.031944 +0000 +0000, created_on:
Failed running “dump”

According to the source the dumper cant find my field in md.columnTypes. At first i thought it an issue with the way the timestamp was stored. But now… after looking at the source i am at a dead-end.

A coworker can run same command with same DB build and is able to do so. So it seems cockroach version ok and so is schema and also format of the timestamp.

Any ideas on what i should look into next?

Ended up getting similar error when dumping JSON.

Was caused by an old client version. Embarrassed i didn’t notice it sooner. Im on a Mac so just ran $ brew upgrade cockroach

boom. fixed.

2 Likes