Hi! On 1 Aug 2010, at 16:28, Walter Heck wrote:

regardless of wether or not MariaDB supports it, I'd recommend going with Sphinx or Solr instead. These are separate easy to manage programs that make your fulltext search capabilities _much_ better, faster and lighter.

MariaDB 5.2 will include the Sphinx storage engine. Read more at: http://askmonty.org/wiki/Manual:Sphinx_storage_engine MariaDB supports full-text search in both MyISAM and Aria (the engine formerly known as Maria) -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Browse the Internet in a safer fashion. Download Web of Trust: http://www.mywot.com/ Cross-platform mobile application development from MoSync: http://www.mosync.com/

Hi Monty On 02/08/2010, at 6:54 PM, Michael Widenius wrote:

Walter> regardless of wether or not MariaDB supports it, I'd recommend going Walter> with Sphinx or Solr instead. These are separate easy to manage Walter> programs that make your fulltext search capabilities _much_ better, Walter> faster and lighter.

Agree that for sophisticated indexing Sphinx (and maybe Solr, but I don't know that one that well) is a a better choice.

We have clients using Sphinx, Xapian and Solr. Choice often depends on the development language/environment used, Java apps would tend towards Solr.

That said, if you have a working setup and MyISAM/Aria does the job, it's probably ok to continue using them. (Don't break a working setup :)

Real world feedback: almost all clients we have that use FULLTEXT need to not use it, because - they need the tables to be InnoDB for transactional/consistency reasons; since Aria is not transactional it's not an option. - FULLTEXT performance both for inserts and selects on larger datasets makes it unsuitable. So they have real problems, that need solving. Most have addressed by adapting the app for Sphinx (and sometimes Xapian), in many cases using the PHP or other APIs, sometimes using the Sphinx engine in the 5.0 OurDelta builds because they want to be able to join the results onto other tables. They all report happiness and not having to spend a lot of development effort to getting it to work and actually making a big difference in overall app performance. So my conclusion - no care for Aria. PBXT is higher on the interest list because it's transactional and can participate in a transaction (XA) with InnoDB making it consistent. - no care for FULLTEXT - Sphinx engine in MariaDB 5.2 is important, because users of 5.0 OurDelta have found that useful; some are actually waiting for MariaDB 5.2 so they can upgrade. By 'no care' I mean "in my opinion it's not worthwhile putting further development effort into these things, there are more worthwhile things" For Aria I've noted this before, but I'm happy to explicitly stick FULLTEXT on the same list. thanks Regards, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Exceptional Services for MySQL at a fixed budget. Follow our blog at http://openquery.com/blog/ OurDelta: packages for MySQL and MariaDB @ http://ourdelta.org

Hi Monty On 04/08/2010, at 8:39 AM, Michael Widenius wrote:

<cut>

Arjen> Real world feedback: almost all clients we have that use FULLTEXT need Arjen> to not use it, because Arjen> - they need the tables to be InnoDB for transactional/ consistency Arjen> reasons; since Aria is not transactional it's not an option.

Aria is crash safe and consistent, which should make it an option for a lot of users; Arjen, how often do you need to do rollback on a fulltext index ?

Such a table is not "purely" an index, it just happens to have columns that need such indexing. Data in multiple tables belongs together, and is inserted/updated at the same time. Rollback is relevant/important. Please don't recycle the ancient argument that you don't need transactions, it's not a winner. Cheers, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Exceptional Services for MySQL at a fixed budget. Follow our blog at http://openquery.com/blog/ OurDelta: packages for MySQL and MariaDB @ http://ourdelta.org

Hi Michael, Thanks for the response. I have tested this in our dev environment with Maria engine (MariaDB 5.1.47) and it works. MariaDB is really awesome. I agree with you, that I would use Sphinx or Solr as my last resort. Kind regards, Joshua On Mon, Aug 2, 2010 at 6:54 PM, Michael Widenius wrote:

Hi!

 On Sun, Aug 1, 2010 at 15:08, Joshua Partogi wrote:

...

...

Hi all,

We are currently using MariaDB in one of our products. One thing that we are wondering, does Maria engine currently supports Fulltext search like MyISAM? If currently not implemented yet, will there be any plan to implement fulltext support in MariaDB?

Thank you very  much in advance for your assistance.

Yes, the Aria engine (the new name for Maria engine) supports same fulltext functionality as MyISAM.

...

...

...

...

...

"Walter" == Walter Heck writes:

Walter> regardless of wether or not MariaDB supports it, I'd recommend going Walter> with Sphinx or Solr instead. These are separate easy to manage Walter> programs that make your fulltext search capabilities _much_ better, Walter> faster and lighter.

Agree that for sophisticated indexing Sphinx (and maybe Solr, but I don't know that one that well) is a a better choice.

That said, if you have a working setup and MyISAM/Aria does the job, it's probably ok to continue using them. (Don't break a working setup :)

Regards, Monty

-- http://twitter.com/scrum8