• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Pulsar Connector

    • Getting Started
      • About the DataStax Apache Pulsar™ Connector
        • System requirements
      • Pulsar Connector release notes
      • Installing DataStax Apache Pulsar™ Connector
      • Pulsar Connector single instance quick start
    • Guides and examples
      • Configuration
        • Configuring parallelism
        • Specify writetime timestamp column
        • Setting row-level TTL values from Pulsar fields
        • Pass Pulsar Connector settings directly to the DataStax Java driver
        • Mapping pulsar topics to database tables
          • Determining topic data structure
          • Mapping basic messages to table columns
          • Mapping a message that contain JSON fields
            • Mapping a message that contains both basic and JSON fields
            • Mapping JSON messages
          • Mapping Avro messages
          • Extract Pulsar record header values
          • Mapping messages to table that has a User Defined Type
          • Mapping a topic to multiple tables
          • Multiple topics to multiple tables
          • Provide CQL queries in mappings
          • The now() function in mappings
      • Operations
        • About operating and maintaining the DataStax Connector
        • Scaling the DataStax Apache Pulsar™ Connector
        • Changing the topic or table schema
        • Restarting the DataStax Apache Pulsar™ Connector
        • Displaying the DataStax Apache Pulsar™ Connector configuration
        • Updating the DataStax Apache Pulsar™ Connector configuration
        • Deleting the DataStax Apache Pulsar™ Connector
        • Getting the DataStax Connector status
      • Security
        • Using internal or LDAP authentication
      • DataStax Apache Pulsar™ Connector metrics
      • Troubleshooting
        • Record fails to write
        • Writing fails because of mutation size
        • Data parsing fails
        • Loading balancing datacenter is not specified
    • Reference
      • DataStax Apache Pulsar™ Connector details
      • DataStax connection
      • Pulsar topic-to-table settings
      • Converting date and times for a topic
      • Using the DataStax Apache Pulsar™ Connector with DataStax Enterprise authentication
        • Internal or LDAP authentication
      • SSL encrypted connection
      • Configure error handling
  • DataStax Pulsar Connector
  • Getting Started
  • Installing DataStax Apache Pulsar™ Connector

Installing DataStax Apache Pulsar™ Connector

Install DataStax Apache Pulsar™ Connector from the DataStax distribution tar file using an account that has write access to the Pulsar configuration directory.

The supported operating systems are Linux and macOS.

Supported Apache Pulsar™ versions

Install the DataStax Apache Pulsar™ Connector on Apache Pulsar 2.7.0.

Apache-2.0 license agreement. By downloading this DataStax product, you agree to the terms of the open-source Apache-2.0 license agreement.

Perform the following steps on a Pulsar Connect node:

  1. Download the tar file from the DataStax downloads site. If you agree, enable the Terms checkbox and click the download icon.

  2. Extract the files:

    tar zxf cassandra-enhanced-pulsar-sink-1.4.0.tar.gz

    The following files are unpacked into a directory such as cassandra-enhanced-pulsar-sink-1.4.0:

    LICENSE.txt
    README.md
    THIRD-PARTY.txt
    conf/example.yml
    cassandra-enhanced-pulsar-sink-1.4.0.nar
  3. Create a connectors directory in the Pulsar home directory if it doesn’t exist.

  4. Move the DataStax connector NAR to the Pulsar connectors directory:

    mv installation_location/cassandra-enhanced-pulsar-sink-1.4.0.nar pulsar_home/connectors
  5. Copy the sample example.yml configuration file from cassandra-enhanced-pulsar-sink-1.4.0/conf/ to the Pulsar configuration directory, which is typically the config or etc directory.

  6. Update the settings as necessary.

    If you are using the cloud.secureConnectBundle, ALL subproperties under ssl: must be empty.
  7. Ensure that the user running Pulsar has permission to access the configuration and NAR files.

System requirements Pulsar Connector single instance quick start

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage