Make search index freshness dates reflect successful indexing

Aperta
#677 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend

Direzione di ricerca

Read the requirements in this issue and the related discussions in #675 and #676 first. The issue names History, System > Indexes, NEST indexing stats, and Bonsai and Elastic Cloud, but does not identify source files or tests. Start by locating the date displays and indexing paths; done means agreed semantics are implemented with tests for success, failure, partial success, unknown state, backend selection, and timezone handling.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

The modified/current-as-of dates in History and System > Indexes do not establish when the displayed search data was successfully indexed.

  • All three History pages display DateTime.UtcNow.ToPacificTime().AddMinutes(-5).ToLocalTime(). This advances with the request clock even if indexing has stopped or failed.
  • System > Indexes converts NEST IndexingStats.Time to DateTime. This property reads the index_time string, a cumulative indexing duration rather than a timestamp. The default stats request omits the human-readable field, so the string is null and Convert.ToDateTime(null) returns DateTime.MinValue. When a duration string such as 1s is present, the conversion throws FormatException.

PR #676 intentionally restores the existing date displays, formatting, tooltips, and data behavior at the user's request. The dual-backend work in #675 should not remove this useful UI while its accuracy requirements are unresolved. This issue tracks the accuracy work separately.

Requirements to define

  • Decide what each displayed date means, including the difference between a successful indexing operation and a guarantee that all relevant source changes are searchable.
  • Report dates for the configured read backend and relevant index. Bonsai and Elastic Cloud may have different successful work and failures during dual indexing.
  • Define how failed operations, partial success across batches/indexes/targets, and full-index replacement affect the displayed value. An attempted or partly successful job must not imply that every result is current.
  • Define the unknown or unavailable state and consistent timezone conversion, formatting, and tooltip wording.
  • Preserve a useful date display for users, with tests covering success, failure, partial success, unknown state, backend selection, and timezone handling.

Choose the source and storage of these dates after the requirements are agreed. This issue does not prescribe SQL tracking, durable recovery, retry queues, or cross-process coordination, and does not expand the scope of #675.

Related: #675 and #676.

Lingua principale
C#
Stelle
7
Fork
5
Merge medio
9h 3m
PR unite (30g)
5

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ucdavis/Purchasing

Tutte le issue di ucdavis/Purchasing

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.