Repository navigation
Support FULLTEXT search #1793
Description
Activity
Yes, we will.
Reacted by Shawn Yanimport full text search column error
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.Reacted by XueliLiuShirley- changed the title
[-]future fulltext search support[/-][+]Support FULLTEXT search[/+]on Mar 22, 2019 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
FULLTEXTindex 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.12 remaining items
@munggruel I realize this is very old but I'm re-visiting this idea. Can you provide some information on the use case for this? It's easy to assume what the use cases are but it helps to know more specifically.
If it's not longer relevant to you, any information about the past use case would be helpful too, if you have the time. You're welcome to find me on the community Slack as well.
I'm obviously not @munggruel, but I really need this.
my use case: users record free-form text notes. months or years later they need to search those notes to find out when they mentioned this or that.
currently we have to read through every single one of the notes to find those that contain the substrings that are being searched for. this is obviously very slow.
if TiDB could index ngrams in text, it would be much more efficient to search through free-form text.
Reacted by Sam Dillardif TiDB could index ngrams in text, it would be much more efficient to search through free-form text.
Like this? https://dev.mysql.com/doc/refman/8.0/en/fulltext-search-ngram.html
I would consider theWITH PARSERpart to be the next step after "basic" fulltext index support.Reacted by Kae Verens@kaeverens out of curiosity, do you have an in-house parser for the text or would a databases's default parser be good enough?
in my case, I would be perfectly happy with the default parser. I don't need anything fancy - just a reasonably fast general search.
wondering if this is still happening or skipped.
This would be a great feature to have, especially since planetscale killed its hobby tier.
Reacted by ChangLiu-at, Sayan J. Das, macG, Matheus Lasserre, Roland Ahimbisibwe, Kevin Bulteel, raigo-linna, Everton Crespin da Silva, Wish and ModestasAdding my voice to the masses.
Reacted by Michael Mayer- added a commit that references this issue
on Apr 25, 2025 - added a commit that references this issue
on Apr 29, 2025 - added a commit that references this issue
on May 18, 2025 Some updates:
- https://www.pingcap.com/article/full-text-search-in-tidb-overview-and-key-features/
- https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql/
So this is available on TiDB Cloud Starter and will later be available elsewhere.
Will you have fulltext search support plan in future