BlueBrain / BlueBrain/nexus

Restarting indexing in a composite view, the delay in seconds should not be negative

Open
#3,712 0 comments 0 reactions 0 assignees View on GitHub
bug delta
Dominant language
Scala
Stars
301
Forks
76
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
```
{
"@context": [
"https://bluebrain.github.io/nexus/contexts/metadata.json",
"https://bluebrain.github.io/nexus/contexts/search.json",
"https://bluebrain.github.io/nexus/contexts/statistics.json"
],
"_total": 1,
"_results": [
{
"sourceId": "https://bluebrain.github.io/nexus/vocabulary/searchSource",
"projectionId": "https://bluebrain.github.io/nexus/vocabulary/searchProjection",
"delayInSeconds": -8983125,
"discardedEvents": 2170,
"evaluatedEvents": 135,
"failedEvents": 0,
"lastEventDateTime": "2022-11-15T15:13:26.624Z",
"lastProcessedEventDateTime": "2023-02-27T14:32:11.271Z",
"processedEvents": 2305,
"remainingEvents": 5958,
"totalEvents": 8263
}
```
The instant in the progress may not be correctly updated ?

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by tracing how composite-view indexing calculates the progress response, using the reported delayInSeconds, lastEventDateTime, and lastProcessedEventDateTime values as a reproduction guide. Done means restarting indexing no longer produces a negative delay and the behavior is covered by an appropriate regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.