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.
It's actually two different things. The first patch (to make it possible to change filtering rules at runtime) is relatively easy, so it might as well be implemented, while this approach that you suggest require some work, so it might be done over a longer time-frame. I don't see a problem with doing both, i.e., throw away the first patch once the second one is finished. Just my few cents, Mats Kindahl > > > Cheers, > Arjen. -- Mats Kindahl Lead Software Developer Replication Team MySQL AB, www.mysql.com
begin:vcard fn:Mats Kindahl n:Kindahl;Mats org:Sun Microsystems adr;quoted-printable:;;Tegv=C3=A4gen 3;Storvreta;SE;74334;Sweden email;internet:[EMAIL PROTECTED] title:Lead Replication Software Developer x-mozilla-html:FALSE version:2.1 end:vcard
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
