Drizzle 2011.03.13 GA tarball has been released!

March 15th, 2011 07:54 am (Pacific) by Patrick Crews

Drizzle source tarball version 2011.03.13 has been released.  This is a GA release (and just in time for the ides of March) >: )

* Apologies for any confusion with version 2011.03.12 (see the url for this entry...) and announcements - there was an issue with the release process that necessitated cutting another tarball.  2011.03.13 is good to go

It's been a long and crazy road to get to this point and the team would like to thank everyone that has helped us get here.  Every patch, bug report, and thought-provoking question has been invaluable in getting Drizzle this solid.

For quick summaries of what has been going on with the team, please check out Andrew Hutching's terrific 'Last Week In Drizzle' series

For a general rundown of how we differ from MySQL, see here

Here is a partial list of what you can find inside:

  • Documentation is sphinx-based and available in-tree or online.  It should be noted that they are licensed under Creative Commons!
  • Replication solutions will be log based.  Both file-based and innodb-table based versions of the log are available and have been heavily tested / validated.
  • Native replication available via the slave plugin.  This solution utilizes the innodb-based replication log and has been subjected to significant testing.  Check out a simple example here.  You can check out David Shrewsbury's replication related blog posts here
  • Easy migration from MySQL systems via the Drizzledump tool.
  • Drizzleadmin tool - used to bypass the protocol’s max-connections setting to do tasks such as killing queries or clients.
  • libdrizzle is included in the tree (no longer a separate project) and is BSD licensed
  • ANSI-compliant INFORMATION_SCHEMA
  • DATA_DICTIONARY for custom, Drizzle-specific tables and data
  • Innodb tables by default
  • MyISAM available (temporary tables)
  • Removed archive, blackhole, csv, and other engines (these can be reintroduced if faced with enough demand).
  • HailDB engine = embedded Innodb, but better
  • Pluggable authentication
  • SQLAlchemy integration - we now pass their test suite and use it as part of our build and test system
  • Significant performance improvements
  • Initial work for catalogs
  • And tons more!

Please consult the documentation as a first resource.  Contact us via our mailing lists, launchpad, or IRC if you have any questions

The Drizzle download file can be found here

Drizzle sessions at the 2011 MySQL UC

March 7th, 2011 05:03 pm (Pacific) by Patrick Crews

There are a large number of Drizzle sessions at this years' MySQL UC.  If you want to know more about what you'll be using instead of MySQL in the very near future, come and check them out ; )

The team will be blogging individually about their various presentations in greater detail in the future, so keep an eye out on Planet Drizzle!

Additionally, the Friday after the conference will be Drizzle Developer Day .  It will be a good opportunity to learn more, provide feedback, etc

Here is a 25% discount code to use in case you haven't registered yet:  mys11fsd: http://oreil.ly/goaqst.

Drizzle 2011.03.11 Release Candidate has been released

March 1st, 2011 09:41 am (Pacific) by Patrick Crews

Drizzle source tarball, version 2011.03.11 has been released.  For those of you counting at home, that makes two...two RC's...ah ah hah! : )

While the original plan was to release a GA today, there are still some features we wanted to test more thoroughly before calling things good.  The plan is to have a GA release on 3/14.  The code is amazingly solid at this point and we feel confident in asking people to start to use it seriously.  Please help us test the heck out of Drizzle to get ready for GA!

If you want the latest and greatest Drizzle news, we highly recommend LinuxJedi's Last Week in Drizzle feature.

Most of the work in this release has been polish, polish, and more polish as we near our first GA!

In this release:

  • New native replication solution - the slave plugin!  This allows a Drizzle server to replicate from a master that is using the innodb replication log.  Read more about this here and here
  • Because you asked for it - MySQL BIT operators are back (thanks to Brian Aker for this)
  • Continued work on system variables
  • Continued work on catalogs
  • Continued work on SQLAlchemy dialect / Drizzle interoperability
  • Fixes for various performance regressions
  • Continued work on documentation
  • random query generator integration with new test runner
  • Over 30 bug fixes

The Drizzle download file can be found here.

Drizzle Documentation Blitz

February 21st, 2011 07:54 am (Pacific) by Lee Bieber

We are designating this Wednesday February 23rd as Drizzle documentation review day. All the Drizzle developers will be reviewing our current documentation for technical errors, missing sections and general improvements. We encourage anyone who would like to improve the quality of our docs to join in this effort, contact us on #drizzle on Freenode, send some email to the discussion list (drizzle-discuss@lists.launchpad.net) or file a bug if you spot anything we could improve on.

-Lee

Drizzle 2011.02.10 (RC) tarball has been released

February 15th, 2011 10:10 am (Pacific) by Patrick Crews

Drizzle source tarball, version 2011.02.10 has been released.  We are proud to announce that this is an RC (Release Candidate) release.

With a GA not too far away, we would greatly appreciate folks helping us to check things out.  We have been working hard on a number of features and would like your feedback.

  • New BOOLEAN type
  • New UUID type
  • Drizzle can now fork to background via --daemon: https://bugs.launchpad.net/drizzle/+bug/565053
  • NOTE: Cartesian joins no longer work and will throw an error - this might break some applications.  They can still be achieved via CROSS JOIN or through the use of a WHERE clause.  It was put in place to prevent runaway queries.
  • Innodb transaction log is working and tested.  Both the file-based and innodb-based logs are available.
  • Continued work on system variables
  • Removed lint.am file as Drizzle no longer uses it
  • Continued work on catalogs
  • Continued work on our documentation
  • Various other bug fixes

The Drizzle download file can be found here

Drizzle has moved to Jenkins

February 9th, 2011 11:24 am (Pacific) by Lee Bieber

Yesterday Monty moved us over to Jenkins for our continuous build system. For those of you who might have been following the drama on this situation we hope you will consider moving also!!

Drizzle 2011.02.09 tarball has been released

February 1st, 2011 03:17 pm (Pacific) by Patrick Crews

Drizzle source tarball, version 2011.02.09 has been released.

We'd like to thank everyone that has been providing feedback and bug reports -  please keep them coming!  We are making some huge strides in the quality and availability of our documentation so please be sure to check it out and write up a bug if something is missing or wrong : )
We're also quite excited to have a working SQLAlchemy dialect!  We plan on incorporating more of that project's tests into our own build system soon.  Thanks to Monty Taylor for making this happen.

In this release:

  • Continued progress on catalogs.
  • HailDB now can get rec_per_key index statistics (via HailDB 2.3 cairo API)
  • HailDB now supports ANALYZE for updating table stats
  • drizzledump has added --my-data-is-mangled for handling certain MySQL charset migration issues
  • SQLAlchemy dialect is now available for Drizzle (merged into SQLAlchemy main)
  • new experimental test-runner, dbqp.py, is in the tree for testing.  test-run.pl remains in the tree as our standby while development continues.
  • migrated unittests to boost + additional work on expanding them and their usage.
  • various updates to our online documentation
  • various other bug fixes

The Drizzle download file can be found here

Drizzle 2011.01.08 tarball has been released

January 18th, 2011 01:03 pm (Pacific) by Patrick Crews

Drizzle source tarball, version 2011.01.08 beta has been released.

In this release:
* Bug blitz release 40+ fixes + several others closed out or pending release in the next tarball.

The Drizzle download file can be found here

Drizzle Developer Day 2011

January 17th, 2011 11:48 am (Pacific) by Lee Bieber

Get ready for Drizzle Developer Day 2011! Similar to the previous years it will be the Friday after the MySQL users conference, April 15 - 9:30 a.m. to 5:00 p.m. We are still working on the exact location and will let you know as soon as possible, most likely it will be at or very close to the Santa Clara convention center. We invite anyone interested in providing feedback, implementing new features, helping to fix bugs, or just wanting to learn more about Drizzle to attend.

Make sure to sign up here as soon as possible as space will be limited.

Hope to see you there
-Lee

Results of Drizzle Bug Blitz

January 15th, 2011 09:13 pm (Pacific) by Lee Bieber

We made a lot of really great progress this past week during our bug blitz. Overall Drizzle stability and quality has greatly improved as a result of the blitz. Here are some of the highlights:

  • Started the week with ~150 open bugs, 2 critical and 19 high
  • As of today, we are at ~125 bugs with 5 in Fix Committed state and in the queue to be merged
  • Looking at priority we now have 0 critical, 9 high
  • Over the week we fixed 41, marked 5 as won't fix, 11 as invalid and 1 as duplicate
  • A majority of our crashing bugs were fixed or marked as no longer valid
  • There were 21 new bugs filed this week, higher than normal but it was the result of some great feedback from the Rackspace DBA's who are giving Drizzle a spin.
  • Yes, the numbers won't add up exactly as I had to track this by hand so a few may have slipped by in either direction. Thanks for everyone who helped out, this really made a big impact. While 125 still seems like a lot of bugs, if you look closely many of the bugs marked as Low or Wishlist are code clean up type bugs or very minor issues. Look for the Drizzle team to start doing bug blitz's on a regular basis.

    -Lee