[BUG] The exchange data may be clean up

Open
#335 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
distributed-systems

Research direction

Start by tracing the broker's retention check described in the issue and how it handles exchange data for the public/default namespace. Reproduce the case with no retention policy, then verify that exchange data remains available while namespaces with an explicit retention policy continue to follow that policy.

Written by the indexing model from the issue text.

Description

type/bug

Describe the bug

Currently, the exchange data may be cleaned up if there is no retention policy. For example, if the namespace public/default didn't set a retention policy, the data of exchange belonging to this namespace will be cleaned up when the broker checks retention.

Dominant language
Java
Stars
123
Forks
41
Avg merge
4h 43m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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 streamnative/aop

All issues in streamnative/aop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.