@Timothy Spann @Greg Keys This is a known issue with HDF-3.0.1 release and we fixed did a release HDF-3.0.1.1. Please find the details here http://dev.hortonworks.com.s3.amazonaws.com/HDPDocuments/HDF3/HDF-3.0.1.1/bk_release-notes/content/ch_hdf_relnotes.html#repo-location. 1. Take a backup of existing SAM app. You can export the app to your local computer. 2. Upgrade the cluster to 3.0.1.1 3. If you have existing data in a Kafka topic that was ingested with the above bug. Make sure you create a new topic or delete the existing topic. 4. Import the SAM topology, make sure you configure the topic and other cluster details in the app. ... View more

@Lester Martin Work around is to add the following in your pom.xml <dependency> <groupId>org.apache.storm</groupId> <artifactId>storm-kafka-clients</artifactId> <version>1.1.0.2.6.0.3-8</version> <exclusions> <exclusion> <groupId>org.apache.kafka</groupId> <artifactId>kafka-clients</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.apache.kafka</groupId> <artifactId>kafka-clients</groupId> <version>0.10.0.2.6.0.0-598</version> </dependency> ... View more

@Ward Bekker can you copy bootstrap/notifier-jars/streamline-notifier*.jar onto /tmp/b7ea53f1-77ca-495f-b9f7-ed28f3097ac1.jar and try re-deploying ... View more