• 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
  • Guides and examples
  • Operations
  • Deleting the DataStax Apache Pulsar™ Connector

Deleting the DataStax Apache Pulsar™ Connector

To completely remove the DataStax Apache Pulsar™ Connector:

  1. Delete any sinks associated with the DataStax Apache Pulsar™ Connector:

    bin/pulsar-admin sinks delete --name sink_name --namespace sink_namespace --tenant sink_tenant

    where

    • name - The name of the Pulsar sink.

    • namespace - The namespace in which the sink resides.

    • sink_tenant - The tenant name associated with the sink.

      Example - delete the cass-sink-kv

      bin/pulsar-admin sinks delete \
          --tenant public \
          --namespace default \
          --name dse-sink-kv
      "Deleted successfully"
  2. Stop the Pulsar service:

    bin/pulsar-daemon stop standalone
    doing stop standalone ...
    stopping standalone
    Shutdown is in progress... Please wait...
    Shutdown is in progress... Please wait...
    Shutdown completed.
  3. Remove the DataStax Apache Pulsar™ Connector from the connectors directory:

    rm connectors/cassandra-enhanced-pulsar-sink-1.4.0.nar
  4. Restart the Pulsar service:

    bin/pulsar-daemon start standalone
    doing start standalone ...
    starting standalone, logging to /Users/john.francis/apache-pulsar-2.7.0/logs/pulsar-standalone-jfrancis-rmbp15.log
    Note: Set immediateFlush to true in conf/log4j2.yaml will guarantee the logging event is flushing to disk immediately. The default behavior is switched off due to performance considerations.
    [AppClassLoader@18b4aac2] info AspectJ Weaver Version 1.9.2 built on Wednesday Oct 24, 2018 at 15:43:33 GMT
    [AppClassLoader@18b4aac2] info register classloader sun.misc.Launcher$AppClassLoader@18b4aac2
    [AppClassLoader@18b4aac2] info using configuration file:/Users/john.francis/apache-pulsar-2.7.0/lib/org.apache.pulsar-pulsar-zookeeper-2.7.0.jar!/META-INF/aop.xml
    [AppClassLoader@18b4aac2] info using configuration file:/Users/john.francis/apache-pulsar-2.7.0/lib/org.apache.pulsar-pulsar-zookeeper-utils-2.7.0.jar!/META-INF/aop.xml
    [AppClassLoader@18b4aac2] info register aspect org.apache.pulsar.zookeeper.FinalRequestProcessorAspect
    [AppClassLoader@18b4aac2] info register aspect org.apache.pulsar.zookeeper.ZooKeeperServerAspect
    [AppClassLoader@18b4aac2] info register aspect org.apache.pulsar.broker.zookeeper.aspectj.ClientCnxnAspect
Updating the DataStax Apache Pulsar™ Connector configuration Getting the DataStax Connector status

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