# Search Relevance - Backlog & Triage: 2023-08-16

**URL:** <https://forum.opensearch.org/t/search-relevance-backlog-triage-2023-08-16/15556>\
**Category:** Community\
**Tags:** community-meeting\
**Created:** [August 16, 2023, 9:58pm UTC](https://forum.opensearch.org/t/search-relevance-backlog-triage-2023-08-16/15556 "2023-08-16T21:58:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![markcohen](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@markcohen](https://forum.opensearch.org/u/markcohen)\
**Post date:** [August 16, 2023, 9:58pm UTC](https://forum.opensearch.org/t/search-relevance-backlog-triage-2023-08-16/15556/1 "2023-08-16T21:58:55Z")

</div>

Notes: All notes as we take them can be found here: [gist:f4d0c72d5f83e10bf27e0c03b0ab3c9e · GitHub](https://gist.github.com/msfroh/f4d0c72d5f83e10bf27e0c03b0ab3c9e). Copied and pasted here for findability.

**Agenda**

1. Triage: [Search Applications Vertical · GitHub](https://github.com/orgs/opensearch-project/projects/45/views/21)
2. Louis’s RFC [[RFC] [Search Pipeline] Script request processor support non-primitive types · Issue #9200 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/9200)
3. Austin’s SearchResponse Ext PR: [Add SearchExtBuilders to SearchResponse by austintlee · Pull Request #9379 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/pull/9379)

**Notes**  
Attendees: Tim Allison, Andriy Redko, Michael Froh, Louis Chu, Mingshi Liu, Sean Li

- Triage
  - Removed a previously triaged issue from board that belongs to neural-search: cross encodings…
  - [[BUG] match\_phrase\_prefix query on an inner object text field not working](https://github.com/opensearch-project/OpenSearch/issues/9203)

- needs a test case to validate. certainly not expected.
  - [[BUG]multiple index queries error](https://github.com/opensearch-project/OpenSearch/issues/8861)
    - needs more info label was added to get more context about the error itself [@suwei999](https://github.com/suwei999)

- [[FEATURE] Cache search results for unmodified search requests#261](https://github.com/opensearch-project/dashboards-search-relevance/issues/261)
- [[BUG] Total hits value behavior change in the response when using search\_after in paginated search requests](https://github.com/opensearch-project/OpenSearch/issues/9013)
  - found a change to search\_after in commits that may be related…

- [[BUG] Incomplete search results against rollup index composed of data from multiple rollup jobs](https://github.com/opensearch-project/OpenSearch/issues/8866)
  - what is the \_rollup plugin? It’s part of index state management
  - should move the issue to the ISM plugin repo
  - [Search flow enhancements for admission controller](https://github.com/opensearch-project/OpenSearch/issues/8913)
    - Admission controller drops requests to keep a cluster from going down
    - already underway with a plan

  - [[Feature Request] SearchExtBuilder in SearchResponse#9328](https://github.com/opensearch-project/OpenSearch/issues/9328)
    - Assigned to [@austintlee](https://github.com/austintlee)

- [[BUG] Search Comparison Tool should report query execution errors#262](https://github.com/opensearch-project/dashboards-search-relevance/issues/262)
  - Moved to Next column

- RFC Discussion:
  - [[RFC] [Search Pipeline] Script request processor support non-primitive types](https://github.com/opensearch-project/OpenSearch/issues/9200) [@noCharger](https://github.com/noCharger)
    - Please leave feedback/questions on different approaches
    - Big question: how can we do painless script query manipulation?
    - We want to let this sit for a bit and promote this for feedback. Will create a forum post.

Next week, let’s go through all New issues on [Search Applications Vertical · GitHub](https://github.com/orgs/opensearch-project/projects/45/views/1) and see how we want to prioritize.

- For each one, what would be a next step?
- How important is the issue?
- If you see a new issue (or any issue) of interest to you please comment or +1 the issue.