opensearch-project / opensearch-project/data-prepper

[BUG] OpenSearch Serverless Sink does not create index on startup

Open
#4,097 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

breaking change bug
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Describe the bug
When using an OpenSearch Serverless collection in a pipeline in the opensearch sink, the index configured is not created until a document is sent to the pipeline and is indexed into the collection.

To Reproduce
Steps to reproduce the behavior:

  1. Create a pipeline with an opensearch serverless collection as a sink
  2. Observe the index configured in the sink is not created when starting Data Prepper
  3. Send an Event to the pipeline
  4. Observe the document in the collection in the specified index

Expected behavior
The index should be created on startup like it is for non-serverless opensearch sinks

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: [e.g. Ubuntu 20.04 LTS]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the OpenSearch sink startup path and reproduce the issue with an OpenSearch Serverless collection, observing whether the configured index exists before any event is sent. Compare this behavior with non-serverless OpenSearch sinks and identify the existing startup index-creation tests or entry points. Done means the configured index is created when the pipeline starts, before documents arrive.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.