Skip to content

vtctl ApplySchema: Added flag -allow_long_unavailability.#1414

Merged
michael-berlin merged 7 commits into
vitessio:masterfrom
michael-berlin:support_force_flag_in_apply_schema
Jan 4, 2016
Merged

vtctl ApplySchema: Added flag -allow_long_unavailability.#1414
michael-berlin merged 7 commits into
vitessio:masterfrom
michael-berlin:support_force_flag_in_apply_schema

Conversation

@michael-berlin
Copy link
Copy Markdown
Contributor

By default, long running schema changes are rejected. With this new flag, this check can be bypassed and the changes applied anyway. As the name of the flag suggests, this can result in a longer period of unavailability.

The first commit is from Shengzhe from: #1241

@alainjobart

yaoshengzhe and others added 7 commits January 4, 2016 15:42
There is currently no big schema change support in open source;
therefore, it is better to allow schema manager to do big schema changes
without enfocing 100,000 rows limit. Add flag "-force" for vtctl command
"ApplySchema" so it accepts big schema changes.
schemamanager: Log warning that the flag is set only if it's actually a big schema.

Added integration test using VtctlPipe. The test is based on copy_schema_shard_test.go.
…ed "null".

Fixed this by removing the unused return value tmutils.SchemaChangeResult from the ApplySchema wrangler command.
@alainjobart
Copy link
Copy Markdown
Contributor

Great change, thanks for the associated clean-up. LGTM.

michael-berlin added a commit that referenced this pull request Jan 4, 2016
…ply_schema

vtctl ApplySchema: Added flag -allow_long_unavailability.
@michael-berlin michael-berlin merged commit e5d4f75 into vitessio:master Jan 4, 2016
@michael-berlin michael-berlin deleted the support_force_flag_in_apply_schema branch January 4, 2016 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants