Two different things, AFAICT. One blueprint is about making configuration changes (for anything) fully online. One that you suggest is specific to replication, no?
Arjen Lentz wrote: > Hi Jay > > On 06/09/2008, at 3:26 AM, Jay Pipes wrote: >> Great points, and certainly something that many have asked for. I went >> ahead and added a Blueprint task for this so that developers can target >> code and branches towards this: >> >> https://blueprints.launchpad.net/drizzle/+spec/runtime-configuration-changes >> > > > Actually, replication filtering came up a few weeks back, and I noted > that it's annoying to have the filtering either client-side or messing > with what gets logged on the server-side. In the brief discussion that > followed we found that a) people agreed with the assessment and b) the > general consensus was that we could make a slave-configured filtering > profile that gets sent to the master on connect which then gets used for > that slave connection. > So while this is new foo, it seriously cleans up all the > replicate/ignore blah which is, really, a big ugly mess to deal with in > the real world. > > I'd much prefer a blueprint in this direction, rather than tweaking the > brokenness. > > > Cheers, > Arjen. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
