Skip to content

Conversation

@poorbarcode
Copy link
Contributor

Motivation

V1 topic creation is allowed even if the namespace does not exist. After a topic creation, users will get the following concerns

  • users will get a namespace not found error when calling pulsar-admin topics list <v1 namespace>
  • users will get an empty list when calling pulsar-admin topics list <v2 namespace>

Modifications

  • fix the bug.

Documentation

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

Matching PR in forked repository

PR in forked repository: x

@poorbarcode poorbarcode added this to the 4.2.0 milestone Oct 22, 2025
@poorbarcode poorbarcode self-assigned this Oct 22, 2025
@poorbarcode poorbarcode added type/bug The PR fixed a bug or issue reported a bug ready-to-test release/4.1.2 release/4.0.8 labels Oct 22, 2025
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Oct 22, 2025
@poorbarcode poorbarcode force-pushed the fix/v1_topic_creation branch from 0c5a911 to e046576 Compare October 27, 2025 02:10
@lhotari
Copy link
Member

lhotari commented Oct 31, 2025

This test failure might be related to the changes:

  Error:  Failures: 
  Error:  org.apache.pulsar.broker.admin.AdminApiSchemaTest.getTopicIntervalStateIncludeSchemaStoreLedger
  [INFO]   Run 1: PASS
  Error:    Run 2: AdminApiSchemaTest.getTopicIntervalStateIncludeSchemaStoreLedger:292 » NotFound V1 namespace [schematest/test] does not exist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-not-needed Your PR changes do not impact docs ready-to-test release/4.0.9 release/4.1.3 type/bug The PR fixed a bug or issue reported a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants