Facebook recently made opensource, osquery. It gives you operating system data via SQL queries! Its very neat, and you can test this even on MacOSX (it works on that platform & Linux). It is by far the project with the most advanced functionality, linked here in this post.
I noticed that rather quickly, there was a PostgreSQL project, called pgosquery, based on Foreign Data Wrappers with a similar idea. (apparently it was written in less than 15 minutes; so a much lower learning curve than the regular MySQL storage engine interface)
I immediately thought about an older MySQL project, by Chip Turner (then at Google, now at Facebook), called mysql-filesystem-engine. This idea was kicking around in 2008. I was intrigued by hearing about this at a talk (probably at the MySQL Conference & Expo); it’s a pity no one took this further.
On a similar tangent, did you also know that there is the option to use MySQL as storage via FUSE (see: mysqlfs)? An article by Ben Martin shows some practical examples.
At its heyday, MySQL had many storage engines (maybe around 50). Wikipedia has an incomplete list. I see some engines on that list, and think that some of these folk are also creating MongoDB backends — competition. At MariaDB we are probably shipping the most storage engines of any MySQL-based distribution, however I think we could be doing an even better job at working with upstream vendors, and figuring out how to support & augment business around it.
I’ve enjoyed visiting Buenos Aires once a year for the MySQLNoSQLCloud event, put together by the awesome people at Binlogic (in particular, their proprietor Santiago Lertora). It’s happening again in 2014, which by my count is the third edition, and there’s a twist: Buenos Aires on 13 & 14 November, and Cordoba on 17 November. It’s never been held in Cordoba before (like an annex event), so I think this could be extremely exciting.
If you’re looking to speak, send Santiago a note at firstname.lastname@example.org (or leave a message here). I’ll put you in touch with him. If you’re looking to sponsor, you get attendees from all over Latin America.
Recently there was a discussion on the webscalesql mailing list started by Chip Turner on a proposed change to the MAX_STATEMENT_TIME patch. This feature has been known as per query variable settings (WL#681) and even shipping in Percona Server 5.6 as per-query variable statement.
This feature has piqued my interest since 2009, when the MySQL project (then owned by Sun Microsystems) participated in Google Summer of Code 2009, and we got code from Joseph Lukas to do just that (see his tree on Launchpad – lp:~jlukas79/+junk/mysql-server).
So code has been floating around since 2009. It never made it into a shipping release of any MySQL-based distribution till 24 October 2013 when Percona Server 5.6.14-62.0 was released. Percona’s syntax implementation was as suggested in WL#681. This got me curious as to if a feature is already shipping in a distribution of MySQL, what is the WebScaleSQL answer to things – is there a look at other branches or is compatibility from a user/DBA perspective only with focus on upstream?
I got my answer from Steaphan Greene. Very sensible, and a great direction to see how the companies involved can influence upstream MySQL and quite obviously the downstream distributions. It is of course great to note that this syntax improvement will probably be in MySQL 5.7.5 DMR (it already is in 5.7.4 DMR).
For what it’s worth, this feature works well alongside server-side statement timeouts, which Percona Server 5.6 implements (as an alpha quality feature) via the Twitter patch of Davi Arnaut. The MySQL team at Oracle has of course been listening, and in MySQL 5.7.4 DMR (release notes) they too have implemented this feature (WL#6936). Kudos!
Update (6 May 2014): Morgan Tocker has opened up mysql#72540.
Via Dave Stokes, MySQL Community Manager:
MySQL Central is truly a MySQL Community show. This year there are five tracks and the majority of the sessions in all the tracks except Performance and Scalability had many more submissions from the MySQL Community than from Oracle/MySQL.
This is impressive. There are about 200 submissions, 50 slots, a 1/4 chance of a talk getting in, and if we follow this logic we will see that MySQL Central @ OpenWorld will truly be a community event (in previous years, majority of the talks came from the MySQL team at Oracle). I can’t wait to see the final program, but as an attendee to the past two MySQL Connect events, I am looking forward to seeing this event grow and be a part of the main program (i.e. not the weekend before).
As Dave says, register now. Though I presume many will wait for the program first. Apparently it is mid-June when speakers will be notified so one can presume an agenda should be out by the end of that month.
While at the keynote of Tomas Ulin at Percona Live MySQL Conference & Expo Santa Clara 2014, he asked the audience what they were running, and most of the audience was on MySQL 5.5 while about 15% of the audience was on MySQL 5.6. This number is steadily increasing I’m sure, so one thing that becomes important is that people will probably start turning on Global Transaction Identifiers (GTIDs).
As you may already know, MariaDB 10 has a different implementation of Global Transaction ID. To me, this poses a problem in a mixed use environment (or even a migration scenario). Which is why MDEV-4487 is so important: it is a feature request to allow replication from MySQL 5.6+ when GTID is enabled on the master.
If you think the issue is important, you can vote and watch the issue on JIRA. I for one think this should be fixed for 10.0.11 or 10.0.12 and not wait for the 10.1 timeframe. Best not to comment here, focus on the JIRA request, MDEV-4487.
There are many MySQL related IRC discussion channels as the ecosystem itself grows. I join the following. Are there any that I’m missing?
- #mysql – main channel for all kinds of end user MySQL related discussions (the noisiest of the lot, naturally)
- #maria – main channel for all kinds of MariaDB related discussions
- #webscalesql – for all kinds of WebScaleSQL discussions
- #percona – main channel for all kinds of Percona related discussions
- #tokutek – main channel for Tokutek discussions (TokuDB or TokuMX)
- SkySQL-specific channels: #maxscale and #mariadb-mgr
- #debian-mysql – for all kinds of Debian MySQL related bits (packaging, bugs, etc.)