Make search index freshness dates reflect successful indexing

Abierto
#677 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C#
Estrellas
7
Forks
5
Merge medio
9 h 3 min
PR fusionados (30 d)
5

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ucdavis/Purchasing

Todos los issues de ucdavis/Purchasing

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.