I think PBXT is the best example till now that the SE API actually works. Paul, who created it, also was not grown in MySQL but he managed to figure out good enough to write a complete transactional general-purpose storage engine.

It did not quite reach GA level. But I don't think the API is to blame. I think Paul needed to turn his efforts towards activities earning him a living (and maybe also he realized that after Oracle's aquisition of Sun that there were no chances that PBXT would be aquired).

But that does not exclude that better and more detailed docs as well as 'guides' would be useful.

-- Peter Laursen

On Mon, Aug 19, 2013 at 5:36 PM, MARK CALLAGHAN <mdcallag@gmail.com> wrote:

Thanks for your response.

On Fri, Aug 16, 2013 at 11:23 AM, Zardosht Kasheff <zardosht@gmail.com> wrote:

I've worked on the TokuDB storage engine for quite a while now. I have
had many experiences over the years, so I guess it's hard to know
where to begin. I guess I will start small, and if the conversation
evolves, I can contribute more thoughts. I think the current API is
really good, as evidenced by the fact that many storage engines have
used it to plug into MySQL. The two areas that I see we can really
benefit from are the following:

Many were written in the long-ago past. Besides TokuDB how many new storage engines have reached GA in the past decade? I worked on a custom storage engine and I am sure others have done the same, but there hasn't been much innovation in the public. Aria is also GA, but that was written by people who know and wrote parts of the API, so it isn't a sign that the API is something people want to use.

Was TokuMX easier to implement than TokuDB?

--
Mark Callaghan
mdcallag@gmail.com

_______________________________________________
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help : https://help.launchpad.net/ListHelp