I'll soon create a PR to change the tests to use V2 formatted topic names.
Besides that, I'm planning to create a PIP to completely remove V1 topic name
format support from Pulsar code base. For existing Pulsar versions, the PIP
could contain a separate solution where it's possible block creation and use of
V1 topics completely.
There's already "allowAutoTopicCreationWithLegacyNamingScheme" option for
blocking the auto-creation of V1 topics, added in
https://github.com/apache/pulsar/pull/23620 (master branch only), but it would
be useful to have more control so that V1 topic usage could be blocked
completely for 4.0.x LTS when configured to do that.
-Lari
On 2025/04/10 08:44:52 Lari Hotari wrote:
> Hi all,
>
> We have a lot of tests that are using the deprecated topic naming
> format V1 such as this one:
>
> persistent://my-property/use/my-ns/my-topic1
>
> This follows the V1 format of:
> {persistent|non-persistent}://{property}/{cluster|global}/{namespace}/{topic}
>
> The V2 naming format was changed already in 2017 in the
> 2.0.0-incubating release (2017-08-08).
> I think it's time to get rid of the V1 topic naming format in the
> majority of the tests.
> We don't even have documentation available for the V1 topic naming format.
> The documentation for V2 naming format is at
> https://pulsar.apache.org/docs/4.0.x/concepts-messaging/#topics.
>
> Another suggestion is to replace "my-property" tenant name with
> "my-tenant" in tests.
> "property" was renamed to "tenant" in 2018 with this PR
> https://github.com/apache/pulsar/pull/1578, so that was already 7
> years ago.
>
> For example:
> persistent://my-property/use/my-ns/my-topic1
> would become:
> persistent://my-tenant/my-ns/my-topic1
>
> I'll create a PR to address this in a single PR.
>
> Another question is, when will we drop support for the undocumented V1
> topic naming format? Is that ever going to happen?
>
> -Lari
>
