[BUG] autocomplete not working when defining a filter

[jfwm2]

What is the bug?
The autocomplete is not working when defining a filter on OpenSearch Dashboards 2.14 (backend is OpenSearch 2.14)

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Go to 'Discover'
2. Click on '+ Add filter'
3. In the 'EDIT FILTER' windows, select a field (“application” in the screenshot provided)
4. Still in the 'EDIT FILTER' windows, choose the operator “is”
5. Still whithin the 'EDIT FILTER' windows, in the “value” text-field, type a letter or more, but the autocomplete does not work
6. Some error 500 are shown in the “chrome debugger” network tab (see screenshot provided)

What is the expected behavior?
A clear and concise description of what you expected to happen.

What is your host/environment?

• OS: CentOS
• Version: 8.8
• Plugins:
  • alertingDashboards@2.14.0.0
  • anomalyDetectionDashboards@2.14.0.0
  • assistantDashboards@2.14.0.0
  • customImportMapDashboards@2.14.0.0
  • ganttChartDashboards@2.14.0.0
  • indexManagementDashboards@2.14.0.0
  • mlCommonsDashboards@2.14.0.0
  • notificationsDashboards@2.14.0.0
  • observabilityDashboards@2.14.0.0
  • queryWorkbenchDashboards@2.14.0.0
  • reportsDashboards@2.14.0.0
  • searchRelevanceDashboards@2.14.0.0
  • securityAnalyticsDashboards@2.14.0.0
  • securityDashboards@2.14.0.0

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.

Do you have any additional context?
Add any other context about the problem.
This behavior was reproduced using various browser, OS

[pgoron]

Hi @jfwm2 , issue seems related to opensearch-project/OpenSearch#14198, worth to check in 2.15.

[dblock]

[Catch All Triage - 1, 2, 3, 4, 5]

[jfwm2]

Indeed upgrading to v2.15 seems to fix the issue. The autocomplete is still slowish but it does the job 👍
Thanks @pgoron!!