Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fix][schema] Only handle exception when there has #20730

Merged
merged 1 commit into from
Jul 6, 2023

Conversation

zymap
Copy link
Member

@zymap zymap commented Jul 6, 2023


Fixes #xyz

Main Issue: #xyz

PIP: #xyz

Motivation

When seeing the warning log, there should have a reason why it shows. But the cause is empty, and the logic is running correctly. We should only print them when the exception is not null.

Modifications

Verifying this change

  • Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository:

---

### Motivation

When seeing the warn log, there should have a reason why
it shows. But the cause is empty and the logic is running
correctly. We should only print them when the exception not
null.
@zymap zymap added this to the 3.1.0 milestone Jul 6, 2023
@zymap zymap self-assigned this Jul 6, 2023
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Jul 6, 2023
@codecov-commenter
Copy link

Codecov Report

Merging #20730 (6d8b61a) into master (ac33311) will increase coverage by 0.15%.
The diff coverage is 57.14%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #20730      +/-   ##
============================================
+ Coverage     73.00%   73.15%   +0.15%     
+ Complexity    32096     3737   -28359     
============================================
  Files          1868     1868              
  Lines        138999   139000       +1     
  Branches      15292    15292              
============================================
+ Hits         101479   101691     +212     
+ Misses        29485    29257     -228     
- Partials       8035     8052      +17     
Flag Coverage Δ
inttests 24.19% <0.00%> (?)
systests 25.03% <0.00%> (-0.07%) ⬇️
unittests 72.43% <57.14%> (+0.04%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...broker/service/schema/BookkeeperSchemaStorage.java 79.39% <57.14%> (+0.67%) ⬆️

... and 78 files with indirect coverage changes

@Technoboy- Technoboy- merged commit 881a1f4 into apache:master Jul 6, 2023
liangyepianzhou pushed a commit that referenced this pull request Jul 7, 2023
nicoloboschi pushed a commit to datastax/pulsar that referenced this pull request Jul 17, 2023
(cherry picked from commit 881a1f4)
(cherry picked from commit b639685)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants