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

PulsarSource does not publish in the correct tenant/namespace #228

Open
brunocascio opened this issue Aug 2, 2024 · 2 comments
Open

PulsarSource does not publish in the correct tenant/namespace #228

brunocascio opened this issue Aug 2, 2024 · 2 comments
Assignees

Comments

@brunocascio
Copy link

Hello folks,

I'm using PulsarSource with RabbitMQ integration everything works ok, but I've noticed seems it's not publishing in the correct tenant/namespace. Instead it is publishing on public/default/<topicName>.

Here's my code:

apiVersion: resource.streamnative.io/v1alpha1
kind: PulsarSource
metadata:
  name: rabbitmq-source
spec:
  className: org.apache.pulsar.io.rabbitmq.RabbitMQSource
  connectionRef:
    name: pulsar-connection
  archive:
    url: https://archive.apache.org/dist/pulsar/pulsar-3.3.0/connectors/pulsar-io-rabbitmq-3.3.0.nar
  configs:
    host: rabbitmq.example.com
    port: "5672"
    virtualHost: myvhost
    queueName: myqueue
    username: myuser
    connectionName: pulsar-connection
    password: mypass
    passive: 'true'
  lifecyclePolicy: CleanUpAfterDeletion
  name: rabbitmq-source
  tenant: mytenant
  namespace: myns
  topicName: mytopic
  parallelism: 1
  processingGuarantees: ATLEAST_ONCE
@ericsyh
Copy link
Member

ericsyh commented Aug 9, 2024

@freeznet Rui, could you help take a look this?

@yash2
Copy link

yash2 commented Nov 13, 2024

Could you pls try replacing with topicName: persistent://mytenant/myns/mytopic instead of topicName: mytopic in your PulsarSource yaml.

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

No branches or pull requests

4 participants