[jira] [Updated] (STORM-2052) Kafka Spout New Client API - Log Improvements and Parameter Tuning for Better Performance
[ https://issues.apache.org/jira/browse/STORM-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-2052: -- Summary: Kafka Spout New Client API - Log Improvements and Parameter Tuning for Better Performance (was: Kafka Spout - New Client API - Log Improvements and Parameter Tuning for Better Performance) > Kafka Spout New Client API - Log Improvements and Parameter Tuning for Better > Performance > - > > Key: STORM-2052 > URL: https://issues.apache.org/jira/browse/STORM-2052 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 1.1.0, 1.0.3, 1.x >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Labels: performance > Time Spent: 1.5h > Remaining Estimate: 0h > > Tune Kafka Spout parameters > Improve Logging to show more meaningful messages, and print detail > appropriate to logging level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2052) Kafka Spout - New Client API - Log Improvements and Parameter Tuning for Better Performance
[ https://issues.apache.org/jira/browse/STORM-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-2052: -- Summary: Kafka Spout - New Client API - Log Improvements and Parameter Tuning for Better Performance (was: Kafka Spout - New Client API - Performance Improvements) > Kafka Spout - New Client API - Log Improvements and Parameter Tuning for > Better Performance > --- > > Key: STORM-2052 > URL: https://issues.apache.org/jira/browse/STORM-2052 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 1.1.0, 1.0.3, 1.x >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Labels: performance > Time Spent: 1.5h > Remaining Estimate: 0h > > Tune Kafka Spout parameters > Improve Logging to show more meaningful messages, and print detail > appropriate to logging level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-2052) Kafka Spout - New Client API - Performance Improvements
[ https://issues.apache.org/jira/browse/STORM-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-2052: -- Affects Version/s: (was: 0.10.2) > Kafka Spout - New Client API - Performance Improvements > --- > > Key: STORM-2052 > URL: https://issues.apache.org/jira/browse/STORM-2052 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 1.1.0, 1.0.3, 1.x >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Labels: performance > > Tune Kafka Spout parameters > Improve Logging to show more meaningful messages, and print detail > appropriate to logging level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-2052) Kafka Spout - New Client API - Performance Improvements
Hugo Louro created STORM-2052: - Summary: Kafka Spout - New Client API - Performance Improvements Key: STORM-2052 URL: https://issues.apache.org/jira/browse/STORM-2052 Project: Apache Storm Issue Type: Bug Components: storm-kafka Affects Versions: 0.10.2, 1.1.0, 1.0.3, 1.x Reporter: Hugo Louro Assignee: Hugo Louro Priority: Critical Tune Kafka Spout parameters Improve Logging to show more meaningful messages, and print detail appropriate to logging level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1695) Create trident spout that uses the new kafka consumer API
[ https://issues.apache.org/jira/browse/STORM-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426213#comment-15426213 ] Hugo Louro commented on STORM-1695: --- Yes. Ideally, this storm-kafka-client will become the de facto, and the old one will eventually be deprecated. > Create trident spout that uses the new kafka consumer API > - > > Key: STORM-1695 > URL: https://issues.apache.org/jira/browse/STORM-1695 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Reporter: Thomas Graves >Assignee: Hugo Louro > > In storm-822 we added a new kafka spout > (org.apache.storm.kafka.spout.KafkaSpout) that uses the new consumer Api in > Kafka 0.9. We decided in that one to handle the Trident support separately. > So this jira is to add Trident support for it similar to what > OpaqueTridentKafkaSpout does for the kafka old consumer api. We need to > support the new consumer api to allow access to a secure Kafka cluster which > was added in Kafka 0.9. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1695) Create trident spout that uses the new kafka consumer API
[ https://issues.apache.org/jira/browse/STORM-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423756#comment-15423756 ] Hugo Louro commented on STORM-1695: --- [~d-t-w] I have already written the code for the Trident Spout. I was just cleaning it up but other stuff came in the way and I didn't raise the PR. I will push it tonight or tomorrow at the latest. > Create trident spout that uses the new kafka consumer API > - > > Key: STORM-1695 > URL: https://issues.apache.org/jira/browse/STORM-1695 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Reporter: Thomas Graves >Assignee: Hugo Louro > > In storm-822 we added a new kafka spout > (org.apache.storm.kafka.spout.KafkaSpout) that uses the new consumer Api in > Kafka 0.9. We decided in that one to handle the Trident support separately. > So this jira is to add Trident support for it similar to what > OpaqueTridentKafkaSpout does for the kafka old consumer api. We need to > support the new consumer api to allow access to a secure Kafka cluster which > was added in Kafka 0.9. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1737) storm-kafka-client has compilation errors with Apache Kafka 0.10
[
https://issues.apache.org/jira/browse/STORM-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371323#comment-15371323
]
Hugo Louro commented on STORM-1737:
---
[~kabhwan] as of release 0.10.0 the @InterfaceStability.Unstable annotation was
removed from the Consumer interface.
I am working on this now. I will a PR by EOD
> storm-kafka-client has compilation errors with Apache Kafka 0.10
>
>
> Key: STORM-1737
> URL: https://issues.apache.org/jira/browse/STORM-1737
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Hugo Louro
>Priority: Blocker
> Fix For: 1.0.2
>
>
> when compiled with Apache Kafka 0.10 branch getting following errors
> {code}
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[163,51]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[166,45]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[175,51]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[177,45]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[252,41]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (STORM-1694) Kafka Spout Trident Implementation Using New Kafka Consumer API
[ https://issues.apache.org/jira/browse/STORM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1694: -- Summary: Kafka Spout Trident Implementation Using New Kafka Consumer API (was: TridentKafkaSpout using new consumer API) > Kafka Spout Trident Implementation Using New Kafka Consumer API > --- > > Key: STORM-1694 > URL: https://issues.apache.org/jira/browse/STORM-1694 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Reporter: Sriharsha Chintalapani >Assignee: Hugo Louro > Fix For: 2.0.0 > > > As part of STORM-822 we addressed the core KafkaSpout with new consumer api. > This JIRA is for trident kafkaSpout with new consumer api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-1930) Kafka New Client API - Support for Topic Wildcards
[ https://issues.apache.org/jira/browse/STORM-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1930: -- Summary: Kafka New Client API - Support for Topic Wildcards (was: Kafka New Client API Support for Topic Wildcards) > Kafka New Client API - Support for Topic Wildcards > -- > > Key: STORM-1930 > URL: https://issues.apache.org/jira/browse/STORM-1930 > Project: Apache Storm > Issue Type: New Feature > Components: storm-kafka >Affects Versions: 1.0.2 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1930) Kafka New Client API Support for Topic Wildcards
Hugo Louro created STORM-1930: - Summary: Kafka New Client API Support for Topic Wildcards Key: STORM-1930 URL: https://issues.apache.org/jira/browse/STORM-1930 Project: Apache Storm Issue Type: New Feature Components: storm-kafka Affects Versions: 1.0.2 Reporter: Hugo Louro Assignee: Hugo Louro Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (STORM-1907) PartitionedTridentSpoutExecutor has incompatible types that cause ClassCastException
[ https://issues.apache.org/jira/browse/STORM-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333063#comment-15333063 ] Hugo Louro edited comment on STORM-1907 at 6/16/16 4:38 AM: I found this issue independently, in my local branch, which was a bit outdated. This patch still makes sense since it gets rid of five warnings that are caused by having ITridentSpout.BatchCoordinator as raw type was (Author: hmclouro): I found this issue independently, in my local branch, which was a bit outdated. > PartitionedTridentSpoutExecutor has incompatible types that cause > ClassCastException > > > Key: STORM-1907 > URL: https://issues.apache.org/jira/browse/STORM-1907 > Project: Apache Storm > Issue Type: Bug > Components: trident >Affects Versions: 1.1.0 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Blocker > > This bug added during the refactor that occurred in this [pull > request|https://github.com/apache/storm/pull/683] > This change causes a ClassCastException cannot cast ArrayList to Integer to > occur when running org.apache.storm.starter.trident.TridentKafkaWordCount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1907) PartitionedTridentSpoutExecutor has incompatible types that cause ClassCastException
[ https://issues.apache.org/jira/browse/STORM-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333063#comment-15333063 ] Hugo Louro commented on STORM-1907: --- I found this issue independently, in my local branch, which was a bit outdated. > PartitionedTridentSpoutExecutor has incompatible types that cause > ClassCastException > > > Key: STORM-1907 > URL: https://issues.apache.org/jira/browse/STORM-1907 > Project: Apache Storm > Issue Type: Bug > Components: trident >Affects Versions: 1.1.0 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Blocker > > This bug added during the refactor that occurred in this [pull > request|https://github.com/apache/storm/pull/683] > This change causes a ClassCastException cannot cast ArrayList to Integer to > occur when running org.apache.storm.starter.trident.TridentKafkaWordCount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-1907) PartitionedTridentSpoutExecutor has incompatible types that cause ClassCastException
[ https://issues.apache.org/jira/browse/STORM-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1907: -- Summary: PartitionedTridentSpoutExecutor has incompatible types that cause ClassCastException (was: PartitionedTridentSpoutExecutor has incompatible types) > PartitionedTridentSpoutExecutor has incompatible types that cause > ClassCastException > > > Key: STORM-1907 > URL: https://issues.apache.org/jira/browse/STORM-1907 > Project: Apache Storm > Issue Type: Bug > Components: trident >Affects Versions: 1.1.0 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Blocker > > This bug added during the refactor that occurred in this [pull > request|https://github.com/apache/storm/pull/683] > This change causes a ClassCastException cannot cast ArrayList to Integer to > occur when running org.apache.storm.starter.trident.TridentKafkaWordCount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1907) PartitionedTridentSpoutExecutor has incompatible types
Hugo Louro created STORM-1907: - Summary: PartitionedTridentSpoutExecutor has incompatible types Key: STORM-1907 URL: https://issues.apache.org/jira/browse/STORM-1907 Project: Apache Storm Issue Type: Bug Components: trident Affects Versions: 1.1.0 Reporter: Hugo Louro Assignee: Hugo Louro Priority: Blocker This bug added during the refactor that occurred in this [pull request|https://github.com/apache/storm/pull/683] This change causes a ClassCastException cannot cast ArrayList to Integer to occur when running org.apache.storm.starter.trident.TridentKafkaWordCount -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-1834) Documentation How to Generate Certificates For Local Testing SSL Setup
[ https://issues.apache.org/jira/browse/STORM-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1834: -- Description: This patch must be cherry picked in 0.10.x-branch, 1.x-branch, and master (was: This patch must be merged in 0.10.x-branch, 1.x-branch, and master) > Documentation How to Generate Certificates For Local Testing SSL Setup > -- > > Key: STORM-1834 > URL: https://issues.apache.org/jira/browse/STORM-1834 > Project: Apache Storm > Issue Type: Bug > Components: documentation >Affects Versions: 1.0.1, 0.10.2 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Trivial > > This patch must be cherry picked in 0.10.x-branch, 1.x-branch, and master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-1834) Documentation How to Generate Certificates For Local Testing SSL Setup
[ https://issues.apache.org/jira/browse/STORM-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1834: -- Description: This patch must be merged in 0.10.x-branch, 1.x-branch, and master > Documentation How to Generate Certificates For Local Testing SSL Setup > -- > > Key: STORM-1834 > URL: https://issues.apache.org/jira/browse/STORM-1834 > Project: Apache Storm > Issue Type: Bug > Components: documentation >Affects Versions: 1.0.1, 0.10.2 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Trivial > > This patch must be merged in 0.10.x-branch, 1.x-branch, and master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1834) Documentation How to Generate Certificates For Local Testing SSL Setup
Hugo Louro created STORM-1834: - Summary: Documentation How to Generate Certificates For Local Testing SSL Setup Key: STORM-1834 URL: https://issues.apache.org/jira/browse/STORM-1834 Project: Apache Storm Issue Type: Bug Components: documentation Affects Versions: 1.0.1, 0.10.2 Reporter: Hugo Louro Assignee: Hugo Louro Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1757) Apache Beam Runner for Storm
[ https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282079#comment-15282079 ] Hugo Louro commented on STORM-1757: --- If it is at all possible unify the APIs for Storm and Trident that would be ideal in my opinion. Ideally the user should have to implement the logic once, and choose how he would like to run it, either streaming (tuples, i.e. using Storm) or batching (Trident). > Apache Beam Runner for Storm > > > Key: STORM-1757 > URL: https://issues.apache.org/jira/browse/STORM-1757 > Project: Apache Storm > Issue Type: Brainstorming >Reporter: P. Taylor Goetz >Priority: Minor > > This is a call for interested parties to collaborate on an Apache Beam [1] > runner for Storm, and express their thoughts and opinions. > Given the addition of the Windowing API to Apache Storm, we should be able to > map naturally to the Beam API. If not, it may be indicative of shortcomings > of the Storm API that should be addressed. > [1] http://beam.incubator.apache.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-1761) Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote Cluster Mode
[ https://issues.apache.org/jira/browse/STORM-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-1761. --- Resolution: Fixed > Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote Cluster > Mode > --- > > Key: STORM-1761 > URL: https://issues.apache.org/jira/browse/STORM-1761 > Project: Apache Storm > Issue Type: Bug > Components: storm-solr >Affects Versions: 1.0.1, 0.10.2 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1761) Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote Cluster Mode
Hugo Louro created STORM-1761: - Summary: Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote Cluster Mode Key: STORM-1761 URL: https://issues.apache.org/jira/browse/STORM-1761 Project: Apache Storm Issue Type: Bug Components: storm-solr Affects Versions: 1.0.1, 0.10.2 Reporter: Hugo Louro Assignee: Hugo Louro Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1757) Apache Beam Runner for Storm
[ https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269498#comment-15269498 ] Hugo Louro commented on STORM-1757: --- I also would like to work on this project. > Apache Beam Runner for Storm > > > Key: STORM-1757 > URL: https://issues.apache.org/jira/browse/STORM-1757 > Project: Apache Storm > Issue Type: Brainstorming >Reporter: P. Taylor Goetz >Priority: Minor > > This is a call for interested parties to collaborate on an Apache Beam [1] > runner for Storm, and express their thoughts and opinions. > Given the addition of the Windowing API to Apache Storm, we should be able to > map naturally to the Beam API. If not, it may be indicative of shortcomings > of the Storm API that should be addressed. > [1] http://beam.incubator.apache.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-1747) storm-kafka-client KafkaSpoutRetryExponentialBackoff throws exception
[
https://issues.apache.org/jira/browse/STORM-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Louro resolved STORM-1747.
---
Resolution: Duplicate
This bug has already been fixed and merged into 1.x-branch. There is currently
a PR based off master.
https://github.com/apache/storm/pull/1382
> storm-kafka-client KafkaSpoutRetryExponentialBackoff throws exception
> -
>
> Key: STORM-1747
> URL: https://issues.apache.org/jira/browse/STORM-1747
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Jifeng Yin
>Assignee: Hugo Louro
>
> {code}
> java.lang.ClassCastException: org.apache.kafka.common.TopicPartition cannot
> be cast to java.lang.Comparable
> at java.util.TreeMap.compare(TreeMap.java:1188) ~[?:1.7.0_80]
> at java.util.TreeMap.put(TreeMap.java:531) ~[?:1.7.0_80]
> at java.util.TreeSet.add(TreeSet.java:255) ~[?:1.7.0_80]
> at
> org.apache.storm.kafka.spout.KafkaSpoutRetryExponentialBackoff.retriableTopicPartitions(KafkaSpoutRetryExponentialBackoff.java:170)
> ~[storm-kafka-client-1.0.0.jar:1.0.0]
> at
> org.apache.storm.kafka.spout.KafkaSpout.doSeekRetriableTopicPartitions(KafkaSpout.java:245)
> ~[storm-kafka-client-1.0.0.jar:1.0.0]
> at
> org.apache.storm.kafka.spout.KafkaSpout.pollKafkaBroker(KafkaSpout.java:236)
> ~[storm-kafka-client-1.0.0.jar:1.0.0]
> at
> org.apache.storm.kafka.spout.KafkaSpout.nextTuple(KafkaSpout.java:202)
> ~[storm-kafka-client-1.0.0.jar:1.0.0]
> at
> org.apache.storm.daemon.executor$fn__7877$fn__7892$fn__7923.invoke(executor.clj:647)
> ~[storm-core-1.0.0.jar:1.0.0]
> at org.apache.storm.util$async_loop$fn__625.invoke(util.clj:484)
> [storm-core-1.0.0.jar:1.0.0]
> at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_80]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (STORM-1737) storm-kafka-client has compilation errors with Apache Kafka 0.10
[
https://issues.apache.org/jira/browse/STORM-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Louro updated STORM-1737:
--
Summary: storm-kafka-client has compilation errors with Apache Kafka 0.10
(was: storm-kaka-client has compilation errors with Apache Kafka 0.10)
> storm-kafka-client has compilation errors with Apache Kafka 0.10
>
>
> Key: STORM-1737
> URL: https://issues.apache.org/jira/browse/STORM-1737
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Hugo Louro
>Priority: Critical
>
> when compiled with Apache Kafka 0.10 branch getting following errors
> {code}
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[163,51]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[166,45]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[175,51]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[177,45]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[252,41]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (STORM-1737) storm-kaka-client has compilation errors with Apache Kafka 0.10
[
https://issues.apache.org/jira/browse/STORM-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Louro updated STORM-1737:
--
Summary: storm-kaka-client has compilation errors with Apache Kafka 0.10
(was: storm-kaka-client has compilation errors with Apache Kafka 0.10 branch)
> storm-kaka-client has compilation errors with Apache Kafka 0.10
> ---
>
> Key: STORM-1737
> URL: https://issues.apache.org/jira/browse/STORM-1737
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Hugo Louro
>Priority: Critical
>
> when compiled with Apache Kafka 0.10 branch getting following errors
> {code}
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[163,51]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[166,45]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[175,51]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[177,45]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> [ERROR]
> /Users/harsha/code/hwx/storm/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java:[252,41]
> incompatible types: org.apache.kafka.common.TopicPartition cannot be
> converted to java.util.Collection
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (STORM-1725) Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap not to throw Exception
[ https://issues.apache.org/jira/browse/STORM-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-1725. --- Resolution: Fixed https://github.com/apache/storm/pull/1357 > Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method > should use HashMap instead of TreeMap not to throw Exception > > > Key: STORM-1725 > URL: https://issues.apache.org/jira/browse/STORM-1725 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 1.0.0 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Blocker > Fix For: 1.0.1 > > > The method > org.apache.storm.kafka.spout.KafkaSpoutRetryExponentialBackoff#retriableTopicPartitions > currently uses TreeMap but TopicPartition does not implement Comparable. > Since ordering is not important, HashMap is the most appropriate data > structure here, and the one I meant to use to begin with. > The fix will replace TreeMap with HashMap. > This issue was found by @jianbzhou and credit should be given to him. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-1725) Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap not to throw Exception
[ https://issues.apache.org/jira/browse/STORM-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1725: -- Summary: Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap not to throw Exception (was: Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap) > Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method > should use HashMap instead of TreeMap not to throw Exception > > > Key: STORM-1725 > URL: https://issues.apache.org/jira/browse/STORM-1725 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 1.0.0 >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Blocker > Fix For: 1.0.1 > > > The method > org.apache.storm.kafka.spout.KafkaSpoutRetryExponentialBackoff#retriableTopicPartitions > currently uses TreeMap but TopicPartition does not implement Comparable. > Since ordering is not important, HashMap is the most appropriate data > structure here, and the one I meant to use to begin with. > The fix will replace TreeMap with HashMap. > This issue was found by @jianbzhou and credit should be given to him. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1725) Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap
Hugo Louro created STORM-1725: - Summary: Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap Key: STORM-1725 URL: https://issues.apache.org/jira/browse/STORM-1725 Project: Apache Storm Issue Type: Bug Components: storm-kafka Affects Versions: 1.0.0 Reporter: Hugo Louro Assignee: Hugo Louro Priority: Blocker Fix For: 1.0.1 The method org.apache.storm.kafka.spout.KafkaSpoutRetryExponentialBackoff#retriableTopicPartitions currently uses TreeMap but TopicPartition does not implement Comparable. Since ordering is not important, HashMap is the most appropriate data structure here, and the one I meant to use to begin with. The fix will replace TreeMap with HashMap. This issue was found by @jianbzhou and credit should be given to him. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-822) Kafka Spout New Consumer API
[ https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-822: - Summary: Kafka Spout New Consumer API (was: As a storm developer I’d like to use the new kafka consumer API (0.8.3) to reduce dependencies and use long term supported kafka apis ) > Kafka Spout New Consumer API > > > Key: STORM-822 > URL: https://issues.apache.org/jira/browse/STORM-822 > Project: Apache Storm > Issue Type: Story > Components: storm-kafka >Reporter: Thomas Becker >Assignee: Hugo Louro > Fix For: 1.0.0, 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-1694) TridentKafkaSpout using new consumer API
[ https://issues.apache.org/jira/browse/STORM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro reassigned STORM-1694: - Assignee: Hugo Louro > TridentKafkaSpout using new consumer API > > > Key: STORM-1694 > URL: https://issues.apache.org/jira/browse/STORM-1694 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Reporter: Sriharsha Chintalapani >Assignee: Hugo Louro > Fix For: 2.0.0 > > > As part of STORM-822 we addressed the core KafkaSpout with new consumer api. > This JIRA is for trident kafkaSpout with new consumer api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-1599) Kafka dependencies all marked as provided (so storm-starter does not run)
[
https://issues.apache.org/jira/browse/STORM-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Louro reassigned STORM-1599:
-
Assignee: Hugo Louro
> Kafka dependencies all marked as provided (so storm-starter does not run)
> -
>
> Key: STORM-1599
> URL: https://issues.apache.org/jira/browse/STORM-1599
> Project: Apache Storm
> Issue Type: Bug
> Components: examples, Flux, storm-kafka
>Affects Versions: 0.10.0, 1.0.0, 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Hugo Louro
>
> When we mark a dependency as provided it indicates the shade and assembly
> plugins to not include this particular dependency in the uber topology jar
> because it will be {provided} on the class path by the system.
> We have been doing this for all of our kafka dependencies incorrectly. This
> means that storm-starter does not have any version of kafka packaged it the
> resulting jar and any example that uses kafka, TridentKafkaWordCount, will
> fail with missing class errors.
> storm-starter/pom.xml has should change its dependency on storm-kafka to be
> compile, and it should delete dependencies on kafka and kafka-clients as
> those should come from storm-kafka as transitive dependencies.
> the main pom.xml should not have kafka-clients marked as provided in the
> dependency management section.
> storm-kafka should remove its provided tag on kafka, and flux examples +
> storm-sql-kafka should remove dependencies on kafka and kafka-clients, and
> storm-kafka should not me marked as provided.
> the flux and sql code I am not as familiar with, but looking at them, and
> running `mvn dependecy:tree` and `mvn dependency:analyze` it looks like
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (STORM-1405) Add Maven 'all-tests' Profile to Travis Script
[ https://issues.apache.org/jira/browse/STORM-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-1405. --- Resolution: Fixed Merged into master. > Add Maven 'all-tests' Profile to Travis Script > -- > > Key: STORM-1405 > URL: https://issues.apache.org/jira/browse/STORM-1405 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Reporter: Hugo Louro >Assignee: Hugo Louro > Fix For: 1.0.0 > > > To run all integration tests as part of the Travis CI build, replace -Pnative > with -Pnative,all-tests in travis-script.sh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1461) Storm.py - Create Tests to Validate CLI Options
Hugo Louro created STORM-1461: - Summary: Storm.py - Create Tests to Validate CLI Options Key: STORM-1461 URL: https://issues.apache.org/jira/browse/STORM-1461 Project: Apache Storm Issue Type: Bug Components: storm-core Reporter: Hugo Louro Assignee: Hugo Louro Fix For: 0.11.0 Typos in function names or CLI options currently go undetected and may cause a valid CLI option not to work when invoked from the CLI. Create a test to validate that a valid CLI calls the correct method and behaves as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1442) Storm Solr Connector - Improve Commit Strategy API and Documentation
Hugo Louro created STORM-1442: - Summary: Storm Solr Connector - Improve Commit Strategy API and Documentation Key: STORM-1442 URL: https://issues.apache.org/jira/browse/STORM-1442 Project: Apache Storm Issue Type: Improvement Components: storm-solr Reporter: Hugo Louro Assignee: Hugo Louro Fix For: 0.11.0 Look at the discussion thread in https://github.com/apache/storm/pull/977 and attachments -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1405) Add Maven 'all-tests' Profile to Travis Script
Hugo Louro created STORM-1405: - Summary: Add Maven 'all-tests' Profile to Travis Script Key: STORM-1405 URL: https://issues.apache.org/jira/browse/STORM-1405 Project: Apache Storm Issue Type: Bug Components: storm-core Reporter: Hugo Louro Assignee: Hugo Louro Fix For: 0.11.0 To run all integration tests as part of the Travis CI build, replace -Pnative with -Pnative,all-tests in travis-script.sh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-1179) Create Maven Profiles for Integration Tests
[ https://issues.apache.org/jira/browse/STORM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-1179. --- Resolution: Fixed Merged into trunk > Create Maven Profiles for Integration Tests > --- > > Key: STORM-1179 > URL: https://issues.apache.org/jira/browse/STORM-1179 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.11.0 >Reporter: Hugo Louro >Assignee: Hugo Louro > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-590) KafkaSpout should use kafka consumer api
[ https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-590: - Assignee: Parth Brahmbhatt (was: Hugo Louro) > KafkaSpout should use kafka consumer api > > > Key: STORM-590 > URL: https://issues.apache.org/jira/browse/STORM-590 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Affects Versions: 0.9.2-incubating >Reporter: Kai Sasaki >Assignee: Parth Brahmbhatt > > Following below ticket > https://github.com/apache/storm/pull/338 > KafkaSpout uses kakfa internal data included zk nodes. However it should be > changed to get these data from kafka consumer api provided kafka project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-590) KafkaSpout should use kafka consumer api
[ https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro reassigned STORM-590: Assignee: Hugo Louro (was: Parth Brahmbhatt) > KafkaSpout should use kafka consumer api > > > Key: STORM-590 > URL: https://issues.apache.org/jira/browse/STORM-590 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Affects Versions: 0.9.2-incubating >Reporter: Kai Sasaki >Assignee: Hugo Louro > > Following below ticket > https://github.com/apache/storm/pull/338 > KafkaSpout uses kakfa internal data included zk nodes. However it should be > changed to get these data from kafka consumer api provided kafka project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-631) Simplifying kafka connector code
[ https://issues.apache.org/jira/browse/STORM-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro reassigned STORM-631: Assignee: Hugo Louro (was: Parth Brahmbhatt) > Simplifying kafka connector code > > > Key: STORM-631 > URL: https://issues.apache.org/jira/browse/STORM-631 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Reporter: Parth Brahmbhatt >Assignee: Hugo Louro > > The current kafka connector was written when kafka did not support any APIs > to expose its internal structures. We already have STORM-590 to modify the > kafka connector to new kafka meta APIS. > The current codebase uses some marker interfaces to support reading kafka > partition/broker info from zookeeper or for users to specify the mapping them > self. Adding one more layer that reads this info using kakfa APIs would > reduce readability. Because we are using marker interfaces there are bunch of > places that has if statements with instanceof checks and each one creates a > separate code path to trace. We should delete these interfaces and their > implementation in favor of a single way to get kafka topic information, using > kafka APIs. This will be a backward incompatible change but should make > future changes and usage easy. > Current kafka connector also has 2 separate configs for trident and core > topologies. This configurations extend from a common interface but the > extensions are not interchangeable. I think it is intuitive to have a single > config with sane defaults for both core and trident spouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-590) KafkaSpout should use kafka consumer api
[ https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro reassigned STORM-590: Assignee: Hugo Louro (was: Parth Brahmbhatt) > KafkaSpout should use kafka consumer api > > > Key: STORM-590 > URL: https://issues.apache.org/jira/browse/STORM-590 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka >Affects Versions: 0.9.2-incubating >Reporter: Kai Sasaki >Assignee: Hugo Louro > > Following below ticket > https://github.com/apache/storm/pull/338 > KafkaSpout uses kakfa internal data included zk nodes. However it should be > changed to get these data from kafka consumer api provided kafka project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1179) Create Maven Profiles for Integration Tests
[ https://issues.apache.org/jira/browse/STORM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046274#comment-15046274 ] Hugo Louro commented on STORM-1179: --- [~sriharsha] [~revans2] [~LongdaFeng] patch has been committed for review > Create Maven Profiles for Integration Tests > --- > > Key: STORM-1179 > URL: https://issues.apache.org/jira/browse/STORM-1179 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.11.0 >Reporter: Hugo Louro >Assignee: Hugo Louro > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (STORM-1179) Create Maven Profiles for Integration Tests
[ https://issues.apache.org/jira/browse/STORM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046274#comment-15046274 ] Hugo Louro edited comment on STORM-1179 at 12/8/15 3:25 AM: [~sriharsha], [~revans2], [~LongdaFeng] patch has been committed for review was (Author: hmclouro): [~sriharsha] [~revans2] [~LongdaFeng] patch has been committed for review > Create Maven Profiles for Integration Tests > --- > > Key: STORM-1179 > URL: https://issues.apache.org/jira/browse/STORM-1179 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.11.0 >Reporter: Hugo Louro >Assignee: Hugo Louro > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1179) Create Maven Profiles for Integration Tests
[ https://issues.apache.org/jira/browse/STORM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993926#comment-14993926 ] Hugo Louro commented on STORM-1179: --- +1 on the the tests format proposed by [~revans2] [~revans2], is it correct to assume that your idea is to have a maven profile for the category of tests in 2) and run these tests from maven passing the desired profile using a CLI property? These tests could be annotated with *@LocalClusterIntegrationTest* and not be run by default when executing mvn clean install. To run the tests annotated by *@LocalClusterIntegrationTest* the user would execute something like: *mvn clean install -P local-cluster-integration-tests* > Create Maven Profiles for Integration Tests > --- > > Key: STORM-1179 > URL: https://issues.apache.org/jira/browse/STORM-1179 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.11.0 >Reporter: Hugo Louro >Assignee: Hugo Louro > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-1179) Create Maven Profiles for Integration and System Tests
Hugo Louro created STORM-1179: - Summary: Create Maven Profiles for Integration and System Tests Key: STORM-1179 URL: https://issues.apache.org/jira/browse/STORM-1179 Project: Apache Storm Issue Type: Bug Components: storm-core Affects Versions: 0.11.0 Reporter: Hugo Louro Assignee: Hugo Louro -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-1179) Create Maven Profiles for Integration Tests
[ https://issues.apache.org/jira/browse/STORM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1179: -- Summary: Create Maven Profiles for Integration Tests (was: Create Maven Profiles for Integration and System Tests) > Create Maven Profiles for Integration Tests > --- > > Key: STORM-1179 > URL: https://issues.apache.org/jira/browse/STORM-1179 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.11.0 >Reporter: Hugo Louro >Assignee: Hugo Louro > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-1179) Create Maven Profiles for Integration Tests
[ https://issues.apache.org/jira/browse/STORM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993064#comment-14993064 ] Hugo Louro commented on STORM-1179: --- [~sriharsha] sure! I was looking at what is done in Kafka, and I know what you mean. But let's talk nevertheless. I have renamed the summary to a more accurate name. > Create Maven Profiles for Integration Tests > --- > > Key: STORM-1179 > URL: https://issues.apache.org/jira/browse/STORM-1179 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 0.11.0 >Reporter: Hugo Louro >Assignee: Hugo Louro > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (STORM-851) Storm Solr connector
[ https://issues.apache.org/jira/browse/STORM-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14717256#comment-14717256 ] Hugo Louro edited comment on STORM-851 at 8/27/15 6:39 PM: --- Merged into trunk. was (Author: hmclouro): Merged into master. Storm Solr connector Key: STORM-851 URL: https://issues.apache.org/jira/browse/STORM-851 Project: Apache Storm Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Hugo Louro Fix For: 0.11.0 Storm solr connector should provide bolt and trident implementation to allow users to index data coming through the topology into solr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-851) Storm Solr connector
[ https://issues.apache.org/jira/browse/STORM-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-851. -- Resolution: Fixed Fix Version/s: 0.11.0 Merged into master. Storm Solr connector Key: STORM-851 URL: https://issues.apache.org/jira/browse/STORM-851 Project: Apache Storm Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Hugo Louro Fix For: 0.11.0 Storm solr connector should provide bolt and trident implementation to allow users to index data coming through the topology into solr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-809) topology.message.timeout.secs should not allow for null or = 0 values
[ https://issues.apache.org/jira/browse/STORM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-809: - Assignee: Robert Joseph Evans (was: Hugo Louro) topology.message.timeout.secs should not allow for null or = 0 values -- Key: STORM-809 URL: https://issues.apache.org/jira/browse/STORM-809 Project: Apache Storm Issue Type: Bug Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans topology.message.timeout.secs has bad things happen if it is set to null or = 0. If it is null killing or rebalancing a topology without providing a timeout results in an NPE. = 0 causes other periodic things to run too frequently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-673) Typo 'deamon' in security documentation
[ https://issues.apache.org/jira/browse/STORM-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-673. -- Resolution: Fixed Merged into master on 02.17.2015 Typo 'deamon' in security documentation --- Key: STORM-673 URL: https://issues.apache.org/jira/browse/STORM-673 Project: Apache Storm Issue Type: Bug Affects Versions: 0.9.3 Reporter: Derek Dagit Priority: Trivial Fix For: 0.10.0 deamon - daemon -- This message was sent by Atlassian JIRA (v6.3.4#6332)
