Lucene query only return two of three documents from index

[bjarnef]

We have the following Lucene query in an Umbraco project:

Category: null, LuceneQuery: {+(+__IndexType:courseinstance) +hideFromSearch:0 +(subjectCode:43541) +isCancelled:0 +(latestValidDate:[638617824000000000 TO 3155378975999990000])}

Which return two results, which page index 0 and page size 100:

But searching in Umbraco backoffice it return three results.

I don't see anything specific regarding the last document besides it is missing a city property.

When searching using Luke this didn't result any results:

+(+__IndexType:courseinstance) +hideFromSearch:0 +(subjectCode:43541) +isCancelled:0 +(latestValidDate:[638617824000000000 TO 3155378975999990000])

but without latestValidDate ranger query:

+(+__IndexType:courseinstance) +hideFromSearch:0 +(subjectCode:43541) +isCancelled:0

Anything specific that could prevent the last index item to be mapped to an ISearchResult?

Examine v3.3.0
Umbraco v13.4.1

[Shazwazza]

This will most likely all boil down to analyzers.

You'll need to describe exactly how your index is configured:

• What analyzer is used
• What field analyzers are used
• ... how to replicate from scratch.

[bjarnef]

For this specific index it is using StandardAnalyzer.

I will see if I can find a way the replicate the issue, but I don't see any specific difference in the three indexed documents besides different values in the fields.

I also find it a bit strange that Luke return three results and Examine search from backoffice (IIRC this use ManageQuery).

[bjarnef]

I had a closer look at the index.

The items has the following latestValidDate:

638730144000000000 -> 2025-01-21​T00:00:00.000Z
638633376000000000 -> 2024-10-01​T00:00:00.000Z
638607456000000000 -> 2024-09-01​T00:00:00.000Z

https://tickstodatetime.azurewebsites.net/

and the query looks like this using DateTime.Now until DateTime.MaxValue:

+(+__IndexType:courseinstance) +hideFromSearch:0 +(subjectCode:43541) +isCancelled:0 +(latestValidDate:[638619552000000000 TO 3155378975999990000])

It seems to correct filter 2 items, but in Umbraco backoffice is doesn't seems the daterange filter has any effect.
E.g. this still return 3 results.

+(+__IndexType:courseinstance) +hideFromSearch:0 +(subjectCode:43541) +isCancelled:0 +(latestValidDate:[3155378975999990000 TO 3155378975999990000])