Open Bug 1795708 Opened 2 years ago Updated 2 years ago

No indication that ongoing global search gloda indexing may cause wrong search results

Categories

(Thunderbird :: Search, defect)

Product:
Thunderbird
Component:
Search
Version:
Thunderbird 102
Type:
defect

Tracking

(Not tracked)

Status:
UNCONFIRMED

People

(Reporter: johnkw, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

Did a "global" search.

Actual results:

Corrupt/incorrect/invalid search results, with partial conversations, and messages listed as being not in the folder they're actually in.

Expected results:

When Thunderbird restarted after a version update, it apparently triggered a complete rebuild of all search databases. Presumably this was needed for some random code internals reason, and that part is fine.

But there needs to be a notice displayed when you perform a search and the search database is in a corrupt/indeterminate state.

Something perhaps like:
"WARNING: Thunderbird is currently collecting search information (which can take several minutes), so the following results are likely to be incomplete or incorrect. The indexing progress can be monitored through the Tools > Activity Manager menu."

Geoff,

  • is it true that updating Thunderbird triggers a complete rebuild of the global database (gloda) for searches?
  • would you think that wrong search results during ongoing gloda indexing can actually happen from the way the indexing process is designed?
Blocks: glodafailtracker
Severity: -- → S3
Flags: needinfo?(geoff)
Summary: no indication of search indexing causing search to be invalid → No indication that ongoing global search gloda indexing may cause wrong search results
Component: Untriaged → Search

(In reply to Thomas D. (:thomas8) from comment #1)

  • is it true that updating Thunderbird triggers a complete rebuild of the global database (gloda) for searches?

Not to my knowledge. It's possible somebody could have made an update trigger a rebuild, but I'm not aware of anybody doing that, or anybody working anywhere near it recently.

  • would you think that wrong search results during ongoing gloda indexing can actually happen from the way the indexing process is designed?

It makes sense that stuff could be missing from search results if it hasn't been indexed yet. But in the wrong folders? Unlikely.

Flags: needinfo?(geoff)
You need to log in before you can comment on or make changes to this bug.