Skip to content

Upon initial rebuild for a new keyspace, also call RebuildVSchema#2573

Merged
alainjobart merged 2 commits intovitessio:masterfrom
HubSpot:rebuild_vschema
Feb 22, 2017
Merged

Upon initial rebuild for a new keyspace, also call RebuildVSchema#2573
alainjobart merged 2 commits intovitessio:masterfrom
HubSpot:rebuild_vschema

Conversation

@bbeaudreault
Copy link
Copy Markdown
Contributor

This fixes #2368

I tested it internally and a newly keyspace with this code is immediately available for queries. Prior to this change, if would fail like so:

E0217 18:31:07.368081 31600 vtctl.go:93] action failed: VtGateExecute Execute failed: keyspace Automation not found in vschema, vtgate: http://5171ab55924c:2097/

This required calling RebuildVSchemaGraph with vtctl before being able to query the keyspace.

@sougou sougou requested a review from alainjobart February 17, 2017 18:41
@alainjobart alainjobart merged commit 17c7f02 into vitessio:master Feb 22, 2017
@bbeaudreault bbeaudreault deleted the rebuild_vschema branch February 22, 2017 15:49
@bbeaudreault
Copy link
Copy Markdown
Contributor Author

thanks!

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.

New keyspaces require a RebuildVSchemaGraph call

3 participants