This might help you Though it can be configured to talk to MySQL automatically, Sphinx is really a separate tool to MyISAM or InnoDB. It offers much better processing and performance than the simplistic fulltext search in MyISAM, but of course the price is that querying with conditions based on both the search and the database at the same time becomes difficult. You can sort of do it using the SphinxSE (storage engine) to query and join via MySQL, but it's not as flexible as keeping it in the database engine and the joins won't perform well. Otherwise, you can take a hybrid approach with MyISAM and InnoDB. Put all your canonical data in the proper InnoDB tables, and just use MyISAM for storing fulltext searchbait. For normal operations you just touch the InnoDB content; only when you're doing a fulltext search do you need to join the MyISAM tables. You then have to make sure you update the MyISAM tables from any new text inserted into the InnoDB tables after a successful transaction.
With these it helps The only problem you may encounter is that MyISAM tables does NOT support transactions. So, if you start transaction, write data to InnoDB and MyISAM tables, then roll it back, changes to INNODB will be rolled back, but changes to MyISAM will not. Also you can consider using something like Sphinx for searches.
MySQL Full-text Search Workaround for innoDB tables