-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
Problem Definition
Currently and for a long while, we've included information messages in the user interface to let the client know their recent changes require a reindex. These messages are not helpful where the client has automated API requests to trigger a reindex as the API isn't letting them know if the reindex is required or not to start with.
Suggested Solution
The client would love either the index summary endpoint to be extended (i.e. api/2/index/summary) or a new one created like a GETtable /rest/api/2/reindex/required that provided a "true" or "false" value to highlight whether a reindex is recommended.
Workaround
No workaround here at present