opensearch-project / opensearch-project/data-prepper

[BUG] Address comments in PR #2673

Open
#2,713 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug

Address comments in PR# 2673

https://github.com/opensearch-project/data-prepper/pull/2673

  • Consumers

  • Indentation issues

  • Remove group_name

  • Pipeline name - we can get that from PipelineDescription

  • Broker URL – This is not working when I change the URL to confluent cloud.. seeing time outs

  • Schema Registry – Unable to connect to Schema Registry- 404 errors resulting in in correct processing of messages for Avro

log:
2023-05-31T11:18:01,130 [log-pipeline-sink-worker-2-thread-1] ERROR org.opensearch.dataprepper.plugins.kafka.source.KafkaSource - GET request failed while fetching the schema registry details : 404
2023-05-31T11:18:01,251 [log-pipeline-sink-worker-2-thread-1] INFO org.opensearch.dataprepper.pipeline.Pipeline - Pipeline [log-pipeline] - Submitting request to initiate the pipeline processing

So consumed messages are

Config@b030ee1 :: 1 executed on : 2023-05-31T11:18:01.251693
{"message":"\u0000\u0000\u0000\u0000\u0002\u0006id0\u0000\u0000\u0000\u0000\u0000@�@"}
{"message":"\u0000\u0000\u0000\u0000\u0002\u0006id1\u0000\u0000\u0000\u0000\u0000@�@"}

  • Auth_type – can you move this to authentication ?

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 by reviewing PR #2673 and the KafkaSource entry point mentioned in the report. Reproduce the Confluent Cloud broker timeout and Schema Registry 404 behavior, then check the listed consumer, configuration, naming, indentation, and authentication concerns. Done means the PR comments are addressed and Avro messages are processed correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kafka
Domain
backend, data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.