In this session, We introduce groonga Storage engine which enables for MySQL to handle fulltext search lightly.
groonga is a library which have storages and indexes for fast fulltext searching. The backend of groonga Storage Engine is groonga library. With groonga Storage Engine, you can use datas in groonga as a usual MySQL tables.
I am a Storage Engine Developer for MySQL in Japan, and the original developer of the Spider Storage Engine and Vertical Partitioning Storage Engine.
Spider Storage Engine and Vertical Partitioning Storage Engine are being offered to the public by GPL.
One of primary authors of Senna/groonga which are embeddable fulltext search engine.
I am a search engine library, groonga, developer in Japan. I participate in developing Groonga Storage Engine.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at yromaine@oreilly.com
For media partnerships, contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference Bulletin (login required).
View a complete list of O'Reilly MySQL Conference Contacts
Comments
High accuracy is the primary difference Sphinx and Groonga.
For example, word ‘mentally’ is handled as same as ‘dfns’ in Sphinx in spite of same word hash value. You can search “This is it” with groonga because of no stop words in groonga.
This sounds great! In your view, what’s the primary difference between Sphinx and Groonga?