Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Design API for Reactive client exceptions and possible translation

Open
  • Is something wrong?
#6 2 comments 1 reaction 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, backend-api-design

Research direction

Start by reviewing the current adapter implementation and the errors thrown by the wrapped Java client. Define and document a stable exception and error-handling model that works for the adapter and a possible native Reactive client. Done means the shared error behavior and translation rules are clearly standardized.

Written by the indexing model from the issue text.

Description

The current adapter implementation wraps the Java client and throws the errors what the Java client throws.

Since the goal is to design a stable API which could be implemented with a native Reactive client later, it is necessary to document and standardize on the error handling and exception model which could be used both in the current adapter approach and later with the native client.

Dominant language
Java
Stars
67
Forks
23
No merged PRs in 30d

Getting set up

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/pulsar-client-reactive

All issues in apache/pulsar-client-reactive

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.