Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions 16/umbraco-cms/reference/searching/examine/indexing.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@

namespace Umbraco.Docs.Samples.Web.CustomIndexing;

[ComposeAfter(typeof(Umbraco.Cms.Infrastructure.Examine.AddExamineComposer))]
public class ExamineComposer : IComposer
{
public void Compose(IUmbracoBuilder builder)
Expand All @@ -63,6 +64,10 @@
}
```

{% hint style="info" %}

Check warning on line 67 in 16/umbraco-cms/reference/searching/examine/indexing.md

View workflow job for this annotation

GitHub Actions / runner / vale

[vale] reported by reviewdog 🐢 [UmbracoDocs.SentenceLength] Write shorter sentences (less than 25 words). For content inside note or warning blocks, add blank lines around the content. Raw Output: {"message": "[UmbracoDocs.SentenceLength] Write shorter sentences (less than 25 words). For content inside note or warning blocks, add blank lines around the content.", "location": {"path": "16/umbraco-cms/reference/searching/examine/indexing.md", "range": {"start": {"line": 67, "column": 4}}}, "severity": "WARNING"}
The use of the `ComposeAfter` attribute guarantees that the composer will run after the core composer responsible for setting up the default index details.
{% endhint %}

### Changing field value types

By default, Examine will store values into the Lucene index as "Full Text" fields, meaning the values will be indexed and analyzed for a textual search. However, if a field value is numerical, date/time, or another non-textual value type, you might want to change how the value is stored in the index. This will let you take advantage of some value type-specific search features such as numerical or date range.
Expand Down
Loading