Vamsi Ch
03/26/2025, 1:57 AMRunLLM
03/26/2025, 1:57 AMbrokerUrl:{8080/8081}/topics/{persistent/non-persistent}/{my-tenant}/{my-namespace}/{my-topic}. This URL format allows you to specify whether the topic is persistent or non-persistent, and includes the tenant, namespace, and topic name.
For example, if you are using a persistent topic, the URL might look like http://localhost:8080/topics/persistent/my-tenant/my-namespace/my-topic. You can use tools like cURL or Postman to send messages to this endpoint.
Would you like more details on how to use this endpoint or any specific configurations?
Sources:
- Pulsar REST 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Vamsi Ch
03/26/2025, 1:26 PMRunLLM
03/26/2025, 1:26 PMimport pulsar
client = pulsar.Client('pulsar://localhost:6650')
consumer = client.subscribe('my-topic', subscription_name='my-sub')
while True:
msg = consumer.receive()
print("Received message: '%s'" % msg.data())
consumer.acknowledge(msg)
client.close()
If you need more information on how to set up a consumer using the Pulsar client libraries, feel free to ask!
Sources:
- Consume a message 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Vamsi Ch
03/26/2025, 1:36 PMRunLLM
03/26/2025, 1:36 PMhttp://broker-address:8080 or https://broker-address:8081 for secure connections.
3. Consult Documentation or Support Channels: If there are specific organizational policies or configurations required for outbound access, refer to any internal documentation or support channels, such as the mentioned Slack channel #outbound_access, for guidance on configuring outbound access.
If you need further assistance with configuring network access or have specific questions about your setup, please let me know!
Sources:
- https://github.com/apache/pulsar/pull/13771
- https://github.com/apache/pulsar/issues/18716 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Vamsi Ch
03/26/2025, 1:40 PMRunLLM
03/26/2025, 1:40 PMpulsar-admin CLI tool. The command to look up the broker URL for a topic is:
bin/pulsar-admin topics lookup persistent://public/default/TestTopic
This command will return the broker URL that is currently serving the specified topic. If you are using a proxy, ensure that the proxy is configured to forward requests to the appropriate broker.
If you need more detailed guidance on using the pulsar-admin tool or configuring your Pulsar setup, feel free to ask!
Sources:
- https://pulsar.apache.org/docs/3.2.x/developing-binary-protocol#docusaurus_skipToContent_fallback
- https://github.com/apache/pulsar/issues/21858 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Vamsi Ch
03/26/2025, 1:42 PMRunLLM
03/26/2025, 1:42 PMpulsar-admin topics lookup command is pulsar://localhost:6650, this indicates that the broker URL for your topic is localhost:6650. To publish messages to the TestTopic using the Pulsar client, you would use this broker URL in your client configuration.
For example, if you are using the Pulsar client library in Python, your code to create a producer might look like this:
import pulsar
client = pulsar.Client('pulsar://localhost:6650')
producer = client.create_producer('persistent://public/default/TestTopic')
producer.send(('Hello Pulsar').encode('utf-8'))
client.close()
This code snippet connects to the broker at localhost:6650 and publishes a message to the TestTopic.
If you are using a REST API to publish messages, you would typically use the HTTP service URL, which might be something like http://localhost:8080 or https://localhost:8081 for secure connections, and then append the topic path to it. However, direct REST API support for publishing messages is limited, and using a client library is recommended for such operations.
Would you like more details on using the Pulsar client library or setting up the REST API?
Sources:
- Pulsar REST 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Vamsi Ch
03/26/2025, 1:50 PMRunLLM
03/26/2025, 1:50 PM