apache / apache/pulsar

[enhancement] avoid log printing when tenant does not exist

Open
#23,742 0 comments 0 reactions 0 assignees View on GitHub
type/enhancement
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Motivation

image

we should throw metadata not found exceptions to avoid printing those ugly stack traces.

### Solution

_No response_

### Alternatives

_No response_

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

The issue does not name any files, tests, or entry points. Start by tracing how requests for a nonexistent tenant handle metadata-not-found conditions and where the stack trace is logged. Done means the appropriate metadata-not-found exception is thrown and the absent-tenant case no longer prints an ugly stack trace.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Feature
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.