From 994e56995ef641ec3a7ab402dd16f4bdb2c6faa3 Mon Sep 17 00:00:00 2001 From: Pallavi <96553709+pallsama@users.noreply.github.com> Date: Wed, 21 Aug 2024 12:34:16 -0700 Subject: [PATCH 1/2] Update 3.yml (#52075) Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> --- data/release-notes/enterprise-server/3-13/3.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/data/release-notes/enterprise-server/3-13/3.yml b/data/release-notes/enterprise-server/3-13/3.yml index d799b63b58..354bdb8c31 100644 --- a/data/release-notes/enterprise-server/3-13/3.yml +++ b/data/release-notes/enterprise-server/3-13/3.yml @@ -117,8 +117,6 @@ sections: When restoring data originally backed up from a 3.13 appliance onto a 3.13 appliance, the elasticsearch indices need to be reindexed before some of the data will show up. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`. - | The global search bar does not have suggestions enabled due to the redesigned navigation and pending new search experience. - - | - Hotpatching in Azure fails with a `rsync` error. - | When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed. - | From 663ecb0109a9461ede5abe2419b0d2a1582b3edf Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Wed, 21 Aug 2024 16:28:30 -0400 Subject: [PATCH 2/2] Launch filtering and aggregate across all versions (#51452) Co-authored-by: Sarah Schneider --- src/search/middleware/contextualize.js | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/search/middleware/contextualize.js b/src/search/middleware/contextualize.js index 5f0c3cf174..20462c06c8 100644 --- a/src/search/middleware/contextualize.js +++ b/src/search/middleware/contextualize.js @@ -46,12 +46,9 @@ export default async function contextualizeSearch(req, res, next) { } } - // Feature flag - if ( - ['enterprise-cloud', 'enterprise-server'].includes(req.context.currentVersion.split('@')[0]) - ) { - search.aggregate = ['toplevel'] - } + // This enables so that when the search is sent to Elasticsearch + // it will request an aggregate by these keyword fields. + search.aggregate = ['toplevel'] req.context.search = { search, validationErrors }