'replication' schema being used vs. actual schema for certain INSERTs with the slave-plugin

Bug #720433 reported by Patrick Crews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
David Shrewsbury
7.0
Fix Released
High
David Shrewsbury

Bug Description

When using the slave plugin, the replication schema is being used vs. the actual schema:
drizzle> select * from applier_state;
+------------------------+---------+------------------------------------------------+
| last_applied_commit_id | status | error_msg |
+------------------------+---------+------------------------------------------------+
| 3 | STOPPED | (SQLSTATE 00000) Unknown table 'replication.A' |
+------------------------+---------+------------------------------------------------+

Related branches

Revision history for this message
Patrick Crews (patrick-crews) wrote :

(SQLSTATE 00000) Unknown table 'replication.A'
Failure while executing:
ALTER TABLE `A` DISABLE KEYS
UPDATE replication.applier_state SET last_applied_commit_id = 3

Due to alter table.

Changed in drizzle:
status: New → Confirmed
assignee: nobody → David Shrewsbury (dshrews)
tags: added: replication
tags: added: slave-plugin
Revision history for this message
David Shrewsbury (dshrews) wrote :

We need to find a way to handle ALTER TABLE when no schema is specified.

Changed in drizzle:
milestone: none → 2011-03-14
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.