Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ALTER TABLE ... SCATTER produces no output #17153

Closed
jordanlewis opened this issue Jul 20, 2017 · 0 comments
Closed

ALTER TABLE ... SCATTER produces no output #17153

jordanlewis opened this issue Jul 20, 2017 · 0 comments
Assignees
@benesch
Milestone
1.1

Comments

@jordanlewis
Copy link
Member

On a 4-node cluster with 100 ranges in kv, the following output occurs:

root@localhost:26257/test> ALTER TABLE kv SCATTER;
+-----+--------+
| key | pretty |
+-----+--------+
+-----+--------+
(0 rows)
@jordanlewis jordanlewis mentioned this issue Aug 1, 2017
Closed
@benesch benesch added this to the 1.1 milestone Aug 1, 2017
@benesch benesch mentioned this issue Aug 2, 2017
Merged
benesch added a commit to benesch/cockroach that referenced this issue Aug 7, 2017
@benesch
storage: restore range information in AdminScatterResponse
59abcf4 
`ALTER TABLE... SCATTER` expects to receive a list of ranges that were
scattered. This information was accidentally dropped in the new
scatter implementation (dbd90cf, cockroachdb#16249). This commit restores the old
behavior, and adds a test to boot.

Fixes cockroachdb#17153.
benesch added a commit to benesch/cockroach that referenced this issue Aug 7, 2017
@benesch
storage: restore range information in AdminScatterResponse
11e25c3 
`ALTER TABLE... SCATTER` expects to receive a list of ranges that were
scattered. This information was accidentally dropped in the new
scatter implementation (dbd90cf, cockroachdb#16249). This commit restores the old
behavior, and adds a test to boot.

Fixes cockroachdb#17153.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benesch benesch

Labels
None yet
Projects
None yet
Milestone
1.1
Development

No branches or pull requests
2 participants
@jordanlewis @benesch