linux-traipu team mailing list archive
-
linux-traipu team
-
Mailing list archive
-
Message #01099
[Bug 811341] Re: `sys_replication`.`applier_state` lacks default values for originating_server_uuid and originating_commit_id
David,
The local server uuid probably is the way to go and the correct
approach. It will need some rework as the server uuid currently isnt
available to the slave plugin, its retrieved from the master host from
the inno replication log.
I can poke at this in the near future. If its a roadblock I would
suggest putting '' for the uuid and linking this bug.
** Changed in: drizzle
Assignee: (unassigned) => Joe Daly (skinny.moey)
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/811341
Title:
`sys_replication`.`applier_state` lacks default values for
originating_server_uuid and originating_commit_id
Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
Confirmed
Bug description:
When the following runs:
INSERT INTO `sys_replication`.`applier_state` (`master_id`, `last_applied_commit_id`, `status`) VALUES (1,0 , 'STOPPED')
We get an error because there are no default values for
originating_server_uuid and originating_commit_id in the
sys_replication.applier_state table.
What should the defaults be?
To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/811341/+subscriptions
References