Skip to main content Skip to complementary content

Apache Pulsar properties

Apache Pulsar connection



Selection Select or enter Pulsar.
Engine Select your engine in the list.
Main URL for Pulsar broker Enter the URL address of your Pulsar broker.

The expected format is the following: pulsar:<host>::<port>

Use SSL encryption Toggle this option ON to enable the SSL encrypted connection.
Authentication Select the way you want to authenticate to your Pulsar broker: either None if you do not require credentials to connect to the broker, or Basic if you need to provide user and password information.
Advanced Connection timeout Sets the maximum number of seconds that a user will wait for a connection to be available. If this time is exceeded and the connection is still unavailable, an exception is thrown.
Description Enter a display name (mandatory) and a description (optional) for the connection.

Apache Pulsar dataset

Property Configuration
Dataset name Enter a display name for the dataset. This name will be used as a unique identifier of the dataset in all Talend Cloud apps.
Connection Select your connection in the list. If you are creating a dataset based on an existing connection, this field is read-only.
Main Message topic Enter the name of the topic (file) to be retrieved.
Consumer name Enter the name of the consumer of your Apache Pulsar message.
Subscription name Enter the identifier of your Apache Pulsar subscription.
Content type format Select in the list the format of the data to be retrieved:
  • CSV: If you select this format, you need to indicate the type of line separator, encoding type and field delimiter used in the file.
    Information noteNote: Space cannot be used as a field separator.
  • Avro: No specific parameters required for this format.
  • JSON: If you select this format, you need to enter the pointer to the JSON data to be retrieved.
  • Raw: No specific parameters required for this format.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!