Skip to content

[cherry-pick][branch-2.9] Cherry-pick #18307 (Fix can not delete namespace by force) - #18803

Merged
congbobo184 merged 3 commits into
apache:branch-2.9from
liangyepianzhou:xiangying/cherry-pick/2.9/delete_namespace_by_force
Dec 8, 2022
Merged

[cherry-pick][branch-2.9] Cherry-pick #18307 (Fix can not delete namespace by force)#18803
congbobo184 merged 3 commits into
apache:branch-2.9from
liangyepianzhou:xiangying/cherry-pick/2.9/delete_namespace_by_force

Conversation

@liangyepianzhou

Copy link
Copy Markdown
Contributor

Motivation

Cherry-pick #18307 for release 2.9.4.

Modifications

Cherry-pick #18307 for release 2.9.4.

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
  • Anything that affects deployment

Documentation

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

@congbobo184
congbobo184 merged commit 06fdbe6 into apache:branch-2.9 Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants