Skip to content

MOD-8129: Fix indexed_percent info stat#5238

Merged
raz-mon merged 1 commit intomasterfrom
razmon-fix_totalKeys
Nov 24, 2024
Merged

MOD-8129: Fix indexed_percent info stat#5238
raz-mon merged 1 commit intomasterfrom
razmon-fix_totalKeys

Conversation

@raz-mon
Copy link
Collaborator

@raz-mon raz-mon commented Nov 21, 2024

The indexed_percent info stat was looking at a potentially not up to date value of the total number of keys in the DB. Since the FT.INFO call is done by the main-thread we can collect this stat on-the-fly such that it is maximally updated.

Also note: The name of the stat is a bit confusing, as this is done in the background. We should consider changing the name to background_indexing_progress.

Mark if applicable

  • This PR introduces API changes
  • This PR introduces serialization changes

@codecov
Copy link

codecov bot commented Nov 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.59%. Comparing base (75feca2) to head (4157067).
Report is 4 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5238      +/-   ##
==========================================
- Coverage   86.59%   86.59%   -0.01%     
==========================================
  Files         193      193              
  Lines       34753    34752       -1     
==========================================
- Hits        30093    30092       -1     
  Misses       4660     4660              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@raz-mon raz-mon requested a review from kei-nan November 21, 2024 14:01
@raz-mon raz-mon added this pull request to the merge queue Nov 24, 2024
Merged via the queue into master with commit 4ad00e8 Nov 24, 2024
@raz-mon raz-mon deleted the razmon-fix_totalKeys branch November 24, 2024 18:46
@redisearch-backport-pull-request
Copy link
Contributor

Backport failed for 2.8, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 2.8
git worktree add -d .worktree/backport-5238-to-2.8 origin/2.8
cd .worktree/backport-5238-to-2.8
git switch --create backport-5238-to-2.8
git cherry-pick -x 4ad00e898ef2c29ea37e89e60527d3418a86aa79

@redisearch-backport-pull-request
Copy link
Contributor

Backport failed for 2.6, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 2.6
git worktree add -d .worktree/backport-5238-to-2.6 origin/2.6
cd .worktree/backport-5238-to-2.6
git switch --create backport-5238-to-2.6
git cherry-pick -x 4ad00e898ef2c29ea37e89e60527d3418a86aa79

@redisearch-backport-pull-request
Copy link
Contributor

Successfully created backport PR for 2.10:

redisearch-backport-pull-request bot pushed a commit that referenced this pull request Nov 24, 2024
Fix indexed_percent info stat

(cherry picked from commit 4ad00e8)
redisearch-backport-pull-request bot pushed a commit that referenced this pull request Nov 24, 2024
Fix indexed_percent info stat

(cherry picked from commit 4ad00e8)
@redisearch-backport-pull-request
Copy link
Contributor

Successfully created backport PR for 8.0:

github-merge-queue bot pushed a commit that referenced this pull request Nov 24, 2024
MOD-8129: Fix indexed_percent info stat (#5238)

Fix indexed_percent info stat

(cherry picked from commit 4ad00e8)

Co-authored-by: Raz Monsonego <[email protected]>
github-merge-queue bot pushed a commit that referenced this pull request Nov 25, 2024
MOD-8129: Fix indexed_percent info stat (#5238)

Fix indexed_percent info stat

(cherry picked from commit 4ad00e8)

Co-authored-by: Raz Monsonego <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants