Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 7

Displaying posts with tag: fulltext (reset)

Fresh dogfood: Migrating to InnoDB fulltext search on bugs.mysql.com
Employee +2 Vote Up -0Vote Down

Even frequent visitors to bugs.mysql.com can sometimes miss the little note in the bottom right corner of each page:

Page generated in 0.017 sec. using MySQL 5.6.11-enterprise-commercial-advanced-log

That text changed this past weekend, going from MySQL Enterprise 5.6.10 to 5.6.11.  But more importantly, the collection of MyISAM tables which support the bugs system were also converted to InnoDB.  There’s a little story to tell here about eating this particular helping of dogfood which also amplifies changelog comments, so here it is:

We like to keep bugs.mysql.com on a current release of MySQL, and

  [Read more...]
OpenSQLCamp Lightning Talk Videos
+3 Vote Up -0Vote Down

OpenSQLCamp was a huge success! Not many folks have blogged about what they learned there….if you missed it, all is not lost. We did take videos of most of the sessions (we only had 3 video cameras, and 4 rooms, and 2 sessions were not recorded).

All the videos have been processed, and I am working on uploading them to YouTube and filling in details for the video descriptions. Not all the videos are up right now….right now all the lightning talks are up.


  [Read more...]
Comparison Between Solr And Sphinx Search Servers (Solr Vs Sphinx – Fight!)
+2 Vote Up -0Vote Down

In the past few weeks I've been implementing advanced search at Plaxo, working quite closely with Solr enterprise search server. Today, I saw this relatively detailed comparison between Solr and its main competitor Sphinx (full credit goes to StackOverflow user mausch who had been using Solr for the past 2 years). For those still confused, Solr and Sphinx are similar to MySQL FULLTEXT search, or for those even more confused, think Google (yeah, this is a bit of a stretch, I know).

Similarities

  • Both Solr and Sphinx satisfy all of your requirements. They're fast and designed to index and search large bodies of data efficiently.
  • Both
  [Read more...]
FULLTEXT and Asian Languages with MySQL 5.0
Employee +1 Vote Up -0Vote Down

I have seen a few people now ask about using MySQL's FULLTEXT indexing with asian languages such as Chinese, Japanese and Korean (herein referred to as CJK.), however, there doesn't seem to be a good centralised article that covers it.

The information is out there, I just don't think it has been well presented yet.

As I have recently done a bunch of research on this topic for a customer, I figured it might be a good opportunity to make my debut in the MySQL blogosphere.

So here we go...

I'll open by saying that attempting to use FULLTEXT with CJK text in MySQL 5.0 will be unsuccessful.

From the CJK FAQ in the MySQL manual:

"For FULLTEXT searches, we need to know where words begin and end. With Western languages, this is rarely a problem because most (if not all) of these use an easy-to-identify word boundary











  [Read more...]
Sphinx - Open Source SQL Full Text Search Engine
+1 Vote Up -0Vote Down

I came across Sphinx today via the MySQL Performance Blog (which has some good entries you might want to check out). It is an Open Source Full Text SQL Search Engine. It can be installed as a storage engine type on MySQL, and from what I hear can beat the pants off of MySQL's built-in full text search in some cases.

From the web site:

Generally, it's a standalone search engine, meant to provide fast, size-efficient and relevant fulltext search functions to other applications. Sphinx was specially designed to integrate well with SQL databases and scripting languages. Currently
  [Read more...]
MySQL FULLTEXT Indexing and Searching
+1 Vote Up -0Vote Down

MySQL has supported FULLTEXT indexes since version 3.23.23. VARCHAR and TEXT Columns that have been indexed with FULLTEXT can be used with special SQL statements that perform the full text search in MySQL.

To get started you need to define the FULLTEXT index on some columns. Like other indexes, FULLTEXT indexes can contain multiple columns. Here's how you might add a FULLTEXT index to some table columns:

ALTER TABLE news ADD FULLTEXT(headline, story);

Once you have a FULLTEXT index, you can search it using MATCH and AGAINST statements. For example:

SELECT headline, story FROM news
WHERE MATCH (headline,story) AGAINST ('Hurricane');

The result of this query is automatically sorted by relevancy.

MATCH

The

  [Read more...]
Two Person Showers
+0 Vote Up -0Vote Down
I've found the two person shower.

No, it does not have two shower heads, but instead takes two people to use. One person gets to take the shower, the other person has to operate the controls since the shower goes from hot to cold every 10 seconds. Even with an operator, the person taking the shower gets scalded and/or frozen every few seconds.

Excellent plumbing job!

BTW we are working on a 5.0 release candidate for MySQL. Sure, this has nothing to do with showers, hot or cold, but it will make Zack happy that I added this to a blog entry since the LJ "post multiplier" sank the planetmysql site and of course nothing was mentioned about 5.0 in any of the multiplied posts.

On a different note I am wondering if Brad is using fulltext for his new auto tag feature, or if he just created his own inverted index method, and if he did, did he use HASH or BTREE indexes on the column?
Showing entries 1 to 7

Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.