github / github/elastomer-client
Add setting to automatically refresh the index
Open
- Dominant language
- Ruby
- Stars
- 197
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Lots of nondeterministic test failures are caused by forgetting to refresh the index after writing or before reading. It would be convenient if elastomer-client had a setting which handled refreshing automatically.
For performance, it could be "smart" and only refresh if a write has happened since the last refresh.
Contributor guide
Research direction
Start by locating elastomer-client's write, read, and index-refresh entry points, then review any existing tests around index visibility. Done means a configurable automatic refresh handles the described write/read cases and avoids refreshing when no write has occurred since the last refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, ruby
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100