Full-text search
The right words.
The relevant records.
Make documents and application content easy to search. Match words and phrases, rank relevant results and bring people straight to the source.
A guide to data access
Define who can read your data and review the access they need.
doc-07 Choose what
a match means.
Start with the search behaviour your users need: all the terms, an exact phrase or a ranked list.
Does it contain every term?
Match records containing all the query words when you need a clear inclusion rule, without relevance ranking.
Explore BooleanDo these words appear together?
Find an exact sequence of words in the same order, useful for names, quoted passages and specific terminology.
Explore PhraseWhich matches are most relevant?
Rank matching content using term frequency, term rarity and document length, then return the leading results.
Explore BM25BM25, phrase search and advanced options require the corresponding full-text capability on your instance. Review feature availability.
Search beside your records
Keep the content
and its context connected.
Use a table full-text index to make selected text searchable. Current engine releases maintain these indexes as rows are inserted, updated and deleted.
Define a full-text indexSearch results carry record IDs, so your application can retrieve the source and follow its relationships.
- 01
Select the text
Choose the fields people need to search in your table.
- 02
Choose the search mode
Match terms, find a phrase or rank results by relevance.
- 03
Open the original record
Use the returned ID to show the matching content and its context.
Using the separate document-index API?
Your application submits text under a document ID and re-indexes it when the source changes. These explicit entries are separate from row-maintained table indexes. Use the original record's ID to keep results connected.
Read the indexing guideRelevance you can understand
Make the best matches
easier to recognize.
Refine how you retrieve content and give people a clearer reason to open a result.
Give the title more say.
Choose field weights in your query to reflect where a match matters most.
Illustrative weighting, not a relevance score.Give fields different weight
Make a title match count differently from a mention in the body, using multi-field weights.
Show why content matches
Use supported BM25 highlights, facets and scoring explanations to help people understand the results.
Express a more precise query
Use the query DSL for supported filters, negation and field-level clauses when a simple search needs more control.
What should I know about search terms and scores?
The simple query endpoint tokenizes and lowercases text. Choose phrase or boolean behaviour through the mode; typed operators such as “AND” or “NOT” are not a query language on that endpoint. Use the DSL for supported structured clauses.
BM25 scores explain relevance within a query. Compare the results for that query, rather than comparing scores between different searches.
Read the search referenceBuild your search experience.
Start with a query, then choose how your application connects.
Build with OriginChainDB