Will you have fulltext search support plan in future
Yes, we will.
import full text search column error
@h1100e Full text search is still on the way.
Does it make sense to support this ? Since when you go lots of distributed data, you may want to use a specialized tool like solr,elasticsearch etc ?
Solr or elastic-search would be a better choice.
Full-text search is on our roadmap. This could make it more convenient for accessing your data in TiDB in a different way. But it is not a high priority feature.
Just a quick update: TiDB 3.0 will not yet support FULLTEXT, but we plan to make it a little clearer that it is not supported: https://github.com/pingcap/tidb/pull/9821
Support FULLTEXT search support 涓枃鍒嗚瘝
@morgo @shenli Any idea how long it might take to implement FULLTEXT? Popular open-source apps like Mattermost need it and our project needs some sort of full text search as well. Just asking before we decide for a strategy. Sending you a complete pull request doesn't seem feasible for now.
@lastzero Thanks for your interest in TiDB. The FULLTEXT index feature is not included in TiDB 4.0 (which will be released in 2020 Q1) plan because of the limited resource. We will consider it in the next year. Community contributions are always welcomed.
@shenli Would you consider adding support to Trigger, so that a Elasticsearch-bridge that maps the updates to the Elasticsearch, like zombodb, can be implemented?
Elasticsearch has very good relevance algorithm and many plugins for different languages, and it is also distributed.
@shenli Will FULLTEXT be supported in 5.0?
@wenfengwang sorry, it is not on the current 5.0 plan. It is a big feature: please thumbs up so we can track relative interest. Thanks!
Most helpful comment
@wenfengwang sorry, it is not on the current 5.0 plan. It is a big feature: please thumbs up so we can track relative interest. Thanks!