[CAMEL-15315] Camel-Pulsar: Error when verifying/creating namespace

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.3, 3.5.0
• Component/s: camel-pulsar

Environment

CentOS 8

Running Pulsar 2.6.0 in a docker container

Spring Boot 2.3.1.RELEASE

Camel version 3.4.0

• Estimated Complexity: Unknown
• Assignee: Andrea Cosentino
• Reporter: James Adam
• Created: 20/Jul/20 10:42
• Updated: 23/Jul/20 16:03
• Resolved: 23/Jul/20 16:03

Description

When starting a spring-based Camel application, The following error is observed:

 

 

2020-07-19 21:33:08.236 ERROR 128775 — [ main] o.a.c.c.pulsar.utils.AutoConfiguration : java.lang.IllegalArgumentException: Invalid namespace format. namespace: default

 

Believe the error is being caused by a bug in the AutoConfiguration class, specifically the ensureNameSpace method: 

 

 

private void ensureNameSpace(String tenant, String namespace) throws PulsarAdminException {
  List<String> namespaces = this.pulsarAdmin.namespaces().getNamespaces(tenant);

  if (!namespaces.contains(namespace)){

      this.pulsarAdmin.namespaces().createNamespace(namespace, this.clusters);

  }

}

 

 

The problem would appear to be that pulsarAdmin.namespaces().getNamespaces(tenant) returns a list of fully qualified namespaces (e.g., "default/public") whereas, the if check is comparing just the namespace alone (e.g. "public") against the fully qualified list. Naturally, this fails, and it then tries to create the namespace (which already exists), feeding it in the wrong format, causing the error to be thrown.

Issue Links

• links to: GitHub Pull Request #4039
• links to: GitHub Pull Request #4040