[ML] Fix pagination reset on search query update. (#65668) (#65815)

Fixes pagination issue: When the query bar query changes, we need to check the selected page is still valid. Example: If you're on a last page (125), edit the filter, and it looks like the grid is trying to reload page 125 even though there are only 24 pages for the new query value you end up with an empty table. This brings over a fix already in place for the transform data grids: On every search query change we'll reset the pagination index.
elastic · May 8, 2020 · 7917703 · 7917703
1 parent 631a33b
commit 7917703
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/...ges/analytics_exploration/components/exploration_results_table/use_exploration_results.ts b/...ges/analytics_exploration/components/exploration_results_table/use_exploration_results.ts
@@ -51,6 +51,10 @@ export const useExplorationResults = (
     d => !d.includes(`.${FEATURE_IMPORTANCE}.`) && d !== ML__ID_COPY
   );
 
+  useEffect(() => {
+    dataGrid.resetPagination();
+  }, [JSON.stringify(searchQuery)]);
+
   useEffect(() => {
     getIndexData(jobConfig, dataGrid, searchQuery);
     // custom comparison

diff --git a/..._analytics/pages/analytics_exploration/components/outlier_exploration/use_outlier_data.ts b/..._analytics/pages/analytics_exploration/components/outlier_exploration/use_outlier_data.ts
@@ -58,6 +58,10 @@ export const useOutlierData = (
     d => !d.includes(`.${FEATURE_INFLUENCE}.`) && d !== ML__ID_COPY
   );
 
+  useEffect(() => {
+    dataGrid.resetPagination();
+  }, [JSON.stringify(searchQuery)]);
+
   // initialize sorting: reverse sort on outlier score column
   useEffect(() => {
     if (jobConfig !== undefined) {