Restructure the Kafka related operators

Open
#469 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, kafka

Research direction

Start by comparing the Kafka-related operators currently in wayang-java and wayang-spark, then review the wayang-platforms structure. The proposal names a new wayang-kafka module containing JavaKafkaOperator and SparkKafkaOperator. Done would mean Kafka implementations are centralized there and the respective platform modules no longer contain Kafka-specific operators.

Written by the indexing model from the issue text.

Description

Proposal:

We create a wayang-kafka module inside of wayang-platforms.
This leads to a cleaner approach to add these operators.

Right now we edit both wayang-java and wayang-spark, where both of them contain versions of operators related to reading and writing to Kafka.

Conceptually, having all implementations for the specific APIs in wayang-kafka would be neat.

Then you could have wayang-kafka/src/main/java/JavaKafkaOperator wayang-kafka/src/main/java/SparkKafkaOperator etc. and the respective platforms themselves don't have to concern about Kafka.

It is planned to implement this as soon as the initial demos for Kafka integration are ready.

Target: Release 1.1 - Q1-2025.

Dominant language
Java
Stars
274
Forks
141
Avg merge
5d 16h
Merged PRs (30d)
4

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.

More from apache/wayang

All issues in apache/wayang

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.