Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
4.0.0
-
Security Level: Public
-
None
-
Untriaged
-
Unknown
Description
Sorry if this is duplicated elsewhere...
At the moment it seems that the completeness percentage is only for the initial build and doesn't take into account the steady-state running of the index and its outstanding mutations.
IMO, the "state" should be separated from the "percentage complete" as the index can be online and servicing queries even if it has not yet caught up with all the incoming mutations...and the user/administrator would want to be able to tell when that is the case.