Drizzle gets all the love right now. MySQL developers who aren't working on Drizzle might feel a little bit unloved. I don't want them to stop what they are doing and move over to Drizzle. I need them to keep on fixing bugs in 5.0 and getting 5.1 ready for GA. So lets share the love. Hug a MySQL developer and let them know you appreciate their hard work -- but only if they are not working on Drizzle.
And speaking of 5.1, what is the plan for releasing 5.1 plugins for Maria and Falcon? Given that the storage engine API supports plugins, the release of a storage engine doesn't require a new server release. InnoDB has already proven that by giving us a plugin that provides compression and fast DDL.
Friday, July 25, 2008
Subscribe to:
Post Comments (Atom)
Posts
Hi Mark!
ReplyDelete"what is the plan for releasing 5.1 plugins for Maria and Falcon? Given that the storage engine API supports plugins, the release of a storage engine doesn't require a new server release. InnoDB has already proven that by giving us a plugin that provides compression and fast DDL."
I would like this too. I don't know if there are plans for that; but now all focus is on releasing 5.1
Hear hear!
ReplyDeleteDrizzle is a side project right now, being done in the spare time of community members *and* some Sun/MySQL employees. That aspect hasn't been clear in some of the blog posts being made, but as far as I know right now, this is an all-volunteer project.
ReplyDeleteI've been talking with MySQL company people about Falcon plugin for 5.1 since last year - also for PBXT actually. It just hasn't been happening, and as you noted the reasons are not technical.
ReplyDeleteSure, I could go and give Monty a hug, he lives quite nearby. Except of course that he and the Maria team are working towards 6.0, so your list doesn't apply - technicalities...
ReplyDeleteWhat I see happening with Drizzle is not so much excitement for the existence of a new MySQL project per se, but rather that finally all the pent up energy for potential community contributions has a meaningful outlet. It seems there are prominent MySQL people out there who are screaming of joy now that there finally is a place they could contribute.
There are many reasons why contributions aren't happening in MySQL nowadays. But a couple are purely technical, for instance using Bitkeeper certainly was a bit anti-social. Another is that the MySQL codebase isn't modular, so it isn't easy to start submitting patches and it wouldn't be easy for MySQL to accept them either. This is what I see in Drizzle. Even if Brian emphasizes it is a stripped down thing for a special use case, I see this as the more modular MySQL which will allow both internal and external developers to move much faster than is now happening. (Think apache 1.x to 2.x) I wouldn't be surprised if Drizzle actually would be the code that becomes MySQL 7 or 8.
Hi Sheeri,
ReplyDeleteThat's a good point about the volunteer nature of Drizzle not being well known. There's a general lack of information around main product direction, so announcements like Drizzle echo more than might otherwise be the case.
...and to Mark:
If history offers any lessons it is that the people working on the flagship tend to be the only ones with a working product. So that's perhaps a consolation to go along with your hug. :)