Add support for Pulsar Transactions
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
- Domain
- api, backend-api-design
Research direction
No files, tests, or entry points are named. Start by reviewing the Reactive Java client's interfaces and the Reactor Context transaction references, then determine how Pulsar transaction context should flow through reactive subscriptions. Done means the client has an agreed, extensible interface design with transaction support and coverage for the relevant flows.
Written by the indexing model from the issue text.
Description
There's currently no support for Pulsar transactions in the Reactive Java client for Apache Pulsar. This is a gap. We should ensure that we have a good way to extend the interfaces for transactions.
Project Reactor has support for passing a context along the Reactive subscription chain. This is used in Spring to pass transaction context in Reactive flows.
Reactive Transactions with Spring were introduced in this blog post: https://spring.io/blog/2019/05/16/reactive-transactions-with-spring .
- Dominant language
- Java
- Stars
- 67
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/pulsar-client-reactive
-
Difficulty 3/5 1-2 days Newbie friendliness 39/100
apache/pulsar-client-reactive#227 ·
-
Acknowledge outside of consumeMany and consumeOneMay be free again @lhotari claimed this 492 days ago, and no pull request is open. Open
apache/pulsar-client-reactive#220 · 1 comment · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
apache/pulsar-client-reactive#216 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/pulsar-client-reactive#182 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/pulsar-client-reactive#114 · 6 comments ·
All issues in apache/pulsar-client-reactive
Similar issues
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
beehive-lab/TornadoVM#1151 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
FasterXML/jackson-dataformats-binary#823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day