Question 1

How to fix 'protoc' not found error when building OpenSearch from source?

Accepted Answer

The build requires the Protocol Buffers compiler (protoc). Install protoc in your environment: on Ubuntu/Debian, run 'sudo apt-get install protobuf-compiler'; on macOS, use 'brew install protobuf'; for GitHub Actions, add a step using 'setup-protoc' action. Alternatively, for Java-only builds, the gradle plugin manages protoc automatically.

Question 2

Why does scripted_metric aggregation throw NullPointerException when used with composite aggregation in OpenSearch 3.3.0+?

Accepted Answer

This is a known regression (issue #21507) introduced by PR #19006 in OpenSearch 3.3.0–3.5.0. The scripted_metric sub-aggregation fails with a NullPointerException on all shards when inside a composite aggregation because the bucket result can be null for empty shards, and the code dereferences result.getClass() before a null check. Workarounds: (1) downgrade to 3.2.0 or earlier, (2) avoid scripted_metric inside composite, or (3) modify your combine_script to return a non‑null default (e.g., `return state == null ? 0 : state.n`) so that the null result is never produced. Track the issue for a permanent fix.

Question 3

How to fix the malicious jqwik 1.10.0 prompt-injection dependency in OpenSearch?

Accepted Answer

OpenSearch is not affected by the reported jqwik issue in its current configuration. `jqwik` is used only as a test-only `propertyTestImplementation` dependency in `sandbox/plugins/analytics-backend-datafusion/build.gradle`; it is not included in the production runtime. The pinned version is `1.9.2`, and `1.9.3` is also unaffected. The hidden ANSI-escaped prompt injection first appears in the `1.10.x` release line.

Mitigation:
1. Do not upgrade to `net.jqwik:jqwik:1.10.0` or later `1.10.x` versions.
2. Keep the dependency pinned to an unaffected version, for example:
   `propertyTestImplementation 'net.jqwik:jqwik:1.9.3'`
3. Verify the resolved version with:
   `./gradlew :sandbox:plugins:analytics-backend-datafusion:dependencies | grep -i jqwik`
4. If AI coding agents process test logs, strip or block ANSI escape sequences and treat log text as untrusted data, not instructions.
5. Pull the OpenSearch build change associated with PR #21906, which resolved the tracking issue.

Question 4

Why does OpenSearch bitmap terms lookup return 0 hits when combined with a filter and text match on a multi-segment index?

Accepted Answer

This is a search bug affecting `terms` lookup with `value_type: "bitmap"` when the query also contains another filter clause and an analyzed `match` query across multiple segments. As a workaround, force-merge the affected index to one segment:

```
POST /index_main/_forcemerge?max_num_segments=1
```

After merging, run the same query again. Other temporary workarounds include moving the text query to `post_filter`, using `wildcard`/`prefix` instead of analyzed `match`, or replacing bitmap lookup with an explicit `terms` array. A permanent fix is tracked in OpenSearch PR #21815; upgrade to a release that includes that PR when available.

Question 5

How do I fix flaky SearchCancellationIT failures in the OpenSearch analytics flow?

Accepted Answer

The flakiness was caused by a deadlock, which was fixed in OpenSearch PR #21771. The `SearchCancellationIT` test was re-enabled in PR #21730. Update your branch or build to include PR #21771 (and the test re-enablement from #21730), then rerun the integration test. As a temporary workaround, rerunning the CI job may pass, but the durable fix is to incorporate the deadlock fix.

OpenSearch

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects