[jira] [Created] (STORM-768) Support JDK 8 compile and runtime.
Kai Sasaki created STORM-768: Summary: Support JDK 8 compile and runtime. Key: STORM-768 URL: https://issues.apache.org/jira/browse/STORM-768 Project: Apache Storm Issue Type: Improvement Affects Versions: 0.11.0 Reporter: Kai Sasaki Assignee: Kai Sasaki storm project support JDK8 compilation and running. There are some check points and tests which should be passed. * Unittests * Server launch * Topology submit and running This might not be enough. Please list up here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (STORM-767) Unresolved dependency in storm-hive
[
https://issues.apache.org/jira/browse/STORM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Sasaki closed STORM-767.
Resolution: Not A Problem
> Unresolved dependency in storm-hive
> ---
>
> Key: STORM-767
> URL: https://issues.apache.org/jira/browse/STORM-767
> Project: Apache Storm
> Issue Type: Bug
>Affects Versions: 0.11.0
>Reporter: Kai Sasaki
>Assignee: Kai Sasaki
>Priority: Minor
> Labels: maven, storm-hive
>
> Building storm-hive fails due to unresolved dependencies about
> {{pentaho-aggdesigner}}.
> {code}
> [ERROR] Failed to execute goal on project storm-hive: Could not resolve
> dependencies for project org.apache.storm:storm-hive:jar:0.11.0-SNAPSHOT:
> Could not find artifact
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde in
> repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/) -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (STORM-767) Unresolved dependency in storm-hive
[
https://issues.apache.org/jira/browse/STORM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491447#comment-14491447
]
Kai Sasaki commented on STORM-767:
--
[~sriharsha] I'm sorry. There might have been some mistake in my side. I cannot
reproduce it.
> Unresolved dependency in storm-hive
> ---
>
> Key: STORM-767
> URL: https://issues.apache.org/jira/browse/STORM-767
> Project: Apache Storm
> Issue Type: Bug
>Affects Versions: 0.11.0
>Reporter: Kai Sasaki
>Assignee: Kai Sasaki
>Priority: Minor
> Labels: maven, storm-hive
>
> Building storm-hive fails due to unresolved dependencies about
> {{pentaho-aggdesigner}}.
> {code}
> [ERROR] Failed to execute goal on project storm-hive: Could not resolve
> dependencies for project org.apache.storm:storm-hive:jar:0.11.0-SNAPSHOT:
> Could not find artifact
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde in
> repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/) -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (STORM-767) Unresolved dependency in storm-hive
Kai Sasaki created STORM-767:
Summary: Unresolved dependency in storm-hive
Key: STORM-767
URL: https://issues.apache.org/jira/browse/STORM-767
Project: Apache Storm
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Kai Sasaki
Assignee: Kai Sasaki
Priority: Minor
Building storm-hive fails due to unresolved dependencies about
{{pentaho-aggdesigner}}.
{code}
[ERROR] Failed to execute goal on project storm-hive: Could not resolve
dependencies for project org.apache.storm:storm-hive:jar:0.11.0-SNAPSHOT: Could
not find artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde in
repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/) -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (STORM-710) bin/storm command list out all the classes in the output for a command
[
https://issues.apache.org/jira/browse/STORM-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368145#comment-14368145
]
Kai Sasaki commented on STORM-710:
--
Why is it unnecessary to remove this type of output when we do running storm
daemons?
It might be useful for debug to see the configuration and environment where the
daemon is running. But I think there are some cases this output is needed when
we storm user command such as {{list}}, {{jar}}. So it will be better to add
some kind of option which decides whether remove this output or not.
> bin/storm command list out all the classes in the output for a command
> --
>
> Key: STORM-710
> URL: https://issues.apache.org/jira/browse/STORM-710
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Oleg Ostashchuk
>Priority: Minor
> Labels: newbie
>
> when running bin/storm list command or any other command it outputs
> Running:
> /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin/java
> -client -Dstorm.options=
> -Dstorm.home=/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT
> -Dstorm.log.dir=/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/logs
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib -Dstorm.conf.file=
> -cp
> /Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/asm-4.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/carbonite-1.4.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/chill-java-0.3.5.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/clj-stacktrace-0.2.7.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/clj-time-0.8.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/clojure-1.6.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/clout-1.0.1.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/commons-codec-1.6.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/commons-exec-1.1.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/commons-fileupload-1.2.1.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/commons-io-2.4.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/commons-lang-2.5.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/commons-logging-1.1.3.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/compojure-1.1.3.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/core.incubator-0.1.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/crypto-equality-1.0.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/crypto-random-1.2.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/disruptor-2.10.1.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/hadoop-auth-2.4.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/hiccup-0.3.6.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/httpclient-4.3.3.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/httpcore-4.3.2.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/java.classpath-0.2.2.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/javax.servlet-2.5.0.v201103041518.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-client-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-continuation-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-http-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-io-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-security-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-server-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-servlet-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-servlets-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jetty-util-7.6.13.v20130916.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/jgrapht-core-0.9.0.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/joda-time-2.3.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/json-simple-1.1.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/kryo-2.21.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/log4j-over-slf4j-1.6.6.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/logback-classic-1.0.13.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/logback-core-1.0.13.jar:/Users/schintalapani/build/apache-storm-0.10.0-SNAPSHOT/lib/math.numeric-tower-
[jira] [Commented] (STORM-695) storm CLI tool reports zero exit code on error scenario, take 2
[
https://issues.apache.org/jira/browse/STORM-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346770#comment-14346770
]
Kai Sasaki commented on STORM-695:
--
[~miguno]Thanks. I'll find out how to do it.
> storm CLI tool reports zero exit code on error scenario, take 2
> ---
>
> Key: STORM-695
> URL: https://issues.apache.org/jira/browse/STORM-695
> Project: Apache Storm
> Issue Type: Bug
>Affects Versions: 0.9.3
>Reporter: Michael Noll
>Assignee: Kai Sasaki
>Priority: Minor
>
> Commands such as "storm kill non-existing-topology" will return an exit code
> of zero, indicating success when in fact the command failed.
> h3. How to reproduce
> Here is but one example where the {{storm}} CLI tool violates shell best
> practices:
> {code}
> # Let's kill a topology that is in fact not running in the cluster.
> $ storm kill i-do-not-exist-topo
>
> Exception in thread "main" NotAliveException(msg:i-do-not-exist-topo is not
> alive)
> # Print the exit code of last command.
> $ echo $?
> 0 # <<< but since the kill command failed this should be non-zero!
> {code}
> Another example is the "storm jar" command. If you attempt to submit a
> topology that has the same name as an existing, running topology, the "storm
> jar" command will not submit the topology -- instead it will print an
> exception (think: "the topology FooName is already running"), which is ok,
> but it will then exit with a return code of zero, which indicates success
> (which is wrong).
> h3. Impact
> This bug prevents automated deployment tools such as Ansible or Puppet as
> well as ad-hoc CLI scripting (think: fire-fighting Ops teams) to work
> properly because Storm violates shell conventions by not returning non-zero
> exit codes in case of failures.
> h3. How to fix
> From what I understand the solution is two-fold:
> # The various Storm commands that are being called by the {{storm}} script
> must return proper exit codes.
> # The {{storm}} script must store these exit codes and return itself with the
> respective exit code of the Storm command it actually ran.
> For example, here's the current code that implements the "storm kill" command:
> {code}
> # In: bin/storm
> def kill(*args):
> """Syntax: [storm kill topology-name [-w wait-time-secs]]
> Kills the topology with the name topology-name. Storm will
> first deactivate the topology's spouts for the duration of
> the topology's message timeout to allow all messages currently
> being processed to finish processing. Storm will then shutdown
> the workers and clean up their state. You can override the length
> of time Storm waits between deactivation and shutdown with the -w flag.
> """
> exec_storm_class(
> "backtype.storm.command.kill_topology",
> args=args,
> jvmtype="-client",
> extrajars=[USER_CONF_DIR, STORM_BIN_DIR])
> {code}
> which in turn calls the following code in {{kill_topology.clj}}:
> {code}
> ;; In: backtype.storm.command.kill-topology
> (ns backtype.storm.command.kill-topology
> (:use [clojure.tools.cli :only [cli]])
> (:use [backtype.storm thrift config log])
> (:import [backtype.storm.generated KillOptions])
> (:gen-class))
> (defn -main [& args]
> (let [[{wait :wait} [name] _] (cli args ["-w" "--wait" :default nil
> :parse-fn #(Integer/parseInt %)])
> opts (KillOptions.)]
> (if wait (.set_wait_secs opts wait))
> (with-configured-nimbus-connection nimbus
> (.killTopologyWithOpts nimbus name opts)
> (log-message "Killed topology: " name)
> )))
> {code}
> which in turn calls the following code in {{nimbus.clj}}:
> {code}
> ;; In: backtype.storm.daemon.nimbus
> (^void killTopologyWithOpts [this ^String storm-name ^KillOptions
> options]
> (check-storm-active! nimbus storm-name true)
> (let [topology-conf (try-read-storm-conf-from-name conf storm-name
> nimbus)]
> (check-authorization! nimbus storm-name topology-conf
> "killTopology"))
> (let [wait-amt (if (.is_set_wait_secs options)
> (.get_wait_secs options)
> )]
> (transition-name! nimbus storm-name [:kill wait-amt] true)
> ))
> {code}
> As you can see the current implementation does not pass success/failure
> information back to the caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (STORM-695) storm CLI tool reports zero exit code on error scenario, take 2
[
https://issues.apache.org/jira/browse/STORM-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Sasaki reassigned STORM-695:
Assignee: Kai Sasaki
> storm CLI tool reports zero exit code on error scenario, take 2
> ---
>
> Key: STORM-695
> URL: https://issues.apache.org/jira/browse/STORM-695
> Project: Apache Storm
> Issue Type: Bug
>Affects Versions: 0.9.3
>Reporter: Michael Noll
>Assignee: Kai Sasaki
>Priority: Minor
>
> Commands such as "storm kill non-existing-topology" will return an exit code
> of zero, indicating success when in fact the command failed.
> h3. How to reproduce
> Here is but one example where the {{storm}} CLI tool violates shell best
> practices:
> {code}
> # Let's kill a topology that is in fact not running in the cluster.
> $ storm kill i-do-not-exist-topo
>
> Exception in thread "main" NotAliveException(msg:i-do-not-exist-topo is not
> alive)
> # Print the exit code of last command.
> $ echo $?
> 0 # <<< but since the kill command failed this should be non-zero!
> {code}
> Another example is the "storm jar" command. If you attempt to submit a
> topology that has the same name as an existing, running topology, the "storm
> jar" command will not submit the topology -- instead it will print an
> exception (think: "the topology FooName is already running"), which is ok,
> but it will then exit with a return code of zero, which indicates success
> (which is wrong).
> h3. Impact
> This bug prevents automated deployment tools such as Ansible or Puppet as
> well as ad-hoc CLI scripting (think: fire-fighting Ops teams) to work
> properly because Storm violates shell conventions by not returning non-zero
> exit codes in case of failures.
> h3. How to fix
> From what I understand the solution is two-fold:
> # The various Storm commands that are being called by the {{storm}} script
> must return proper exit codes.
> # The {{storm}} script must store these exit codes and return itself with the
> respective exit code of the Storm command it actually ran.
> For example, here's the current code that implements the "storm kill" command:
> {code}
> # In: bin/storm
> def kill(*args):
> """Syntax: [storm kill topology-name [-w wait-time-secs]]
> Kills the topology with the name topology-name. Storm will
> first deactivate the topology's spouts for the duration of
> the topology's message timeout to allow all messages currently
> being processed to finish processing. Storm will then shutdown
> the workers and clean up their state. You can override the length
> of time Storm waits between deactivation and shutdown with the -w flag.
> """
> exec_storm_class(
> "backtype.storm.command.kill_topology",
> args=args,
> jvmtype="-client",
> extrajars=[USER_CONF_DIR, STORM_BIN_DIR])
> {code}
> which in turn calls the following code in {{kill_topology.clj}}:
> {code}
> ;; In: backtype.storm.command.kill-topology
> (ns backtype.storm.command.kill-topology
> (:use [clojure.tools.cli :only [cli]])
> (:use [backtype.storm thrift config log])
> (:import [backtype.storm.generated KillOptions])
> (:gen-class))
> (defn -main [& args]
> (let [[{wait :wait} [name] _] (cli args ["-w" "--wait" :default nil
> :parse-fn #(Integer/parseInt %)])
> opts (KillOptions.)]
> (if wait (.set_wait_secs opts wait))
> (with-configured-nimbus-connection nimbus
> (.killTopologyWithOpts nimbus name opts)
> (log-message "Killed topology: " name)
> )))
> {code}
> which in turn calls the following code in {{nimbus.clj}}:
> {code}
> ;; In: backtype.storm.daemon.nimbus
> (^void killTopologyWithOpts [this ^String storm-name ^KillOptions
> options]
> (check-storm-active! nimbus storm-name true)
> (let [topology-conf (try-read-storm-conf-from-name conf storm-name
> nimbus)]
> (check-authorization! nimbus storm-name topology-conf
> "killTopology"))
> (let [wait-amt (if (.is_set_wait_secs options)
> (.get_wait_secs options)
> )]
> (transition-name! nimbus storm-name [:kill wait-amt] true)
> ))
> {code}
> As you can see the current implementation does not pass success/failure
> information back to the caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (STORM-695) storm CLI tool reports zero exit code on error scenario, take 2
[
https://issues.apache.org/jira/browse/STORM-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342955#comment-14342955
]
Kai Sasaki commented on STORM-695:
--
[~miguno] CLI tools cannot handle any errors with current command tool. So I
think it will be needed. But I have a question. Is there anyway to handle
exceptions and errors through thrift interface? Though I am not familiar with
thrift so much, I want to know how to do it. Thank you.
> storm CLI tool reports zero exit code on error scenario, take 2
> ---
>
> Key: STORM-695
> URL: https://issues.apache.org/jira/browse/STORM-695
> Project: Apache Storm
> Issue Type: Bug
>Affects Versions: 0.9.3
>Reporter: Michael Noll
>Priority: Minor
>
> Commands such as "storm kill non-existing-topology" will return an exit code
> of zero, indicating success when in fact the command failed.
> h3. How to reproduce
> Here is but one example where the {{storm}} CLI tool violates shell best
> practices:
> {code}
> # Let's kill a topology that is in fact not running in the cluster.
> $ storm kill i-do-not-exist-topo
>
> Exception in thread "main" NotAliveException(msg:i-do-not-exist-topo is not
> alive)
> # Print the exit code of last command.
> $ echo $?
> 0 # <<< but since the kill command failed this should be non-zero!
> {code}
> Another example is the "storm jar" command. If you attempt to submit a
> topology that has the same name as an existing, running topology, the "storm
> jar" command will not submit the topology -- instead it will print an
> exception (think: "the topology FooName is already running"), which is ok,
> but it will then exit with a return code of zero, which indicates success
> (which is wrong).
> h3. Impact
> This bug prevents automated deployment tools such as Ansible or Puppet as
> well as ad-hoc CLI scripting (think: fire-fighting Ops teams) to work
> properly because Storm violates shell conventions by not returning non-zero
> exit codes in case of failures.
> h3. How to fix
> From what I understand the solution is two-fold:
> # The various Storm commands that are being called by the {{storm}} script
> must return proper exit codes.
> # The {{storm}} script must store these exit codes and return itself with the
> respective exit code of the Storm command it actually ran.
> For example, here's the current code that implements the "storm kill" command:
> {code}
> # In: bin/storm
> def kill(*args):
> """Syntax: [storm kill topology-name [-w wait-time-secs]]
> Kills the topology with the name topology-name. Storm will
> first deactivate the topology's spouts for the duration of
> the topology's message timeout to allow all messages currently
> being processed to finish processing. Storm will then shutdown
> the workers and clean up their state. You can override the length
> of time Storm waits between deactivation and shutdown with the -w flag.
> """
> exec_storm_class(
> "backtype.storm.command.kill_topology",
> args=args,
> jvmtype="-client",
> extrajars=[USER_CONF_DIR, STORM_BIN_DIR])
> {code}
> which in turn calls the following code in {{kill_topology.clj}}:
> {code}
> ;; In: backtype.storm.command.kill-topology
> (ns backtype.storm.command.kill-topology
> (:use [clojure.tools.cli :only [cli]])
> (:use [backtype.storm thrift config log])
> (:import [backtype.storm.generated KillOptions])
> (:gen-class))
> (defn -main [& args]
> (let [[{wait :wait} [name] _] (cli args ["-w" "--wait" :default nil
> :parse-fn #(Integer/parseInt %)])
> opts (KillOptions.)]
> (if wait (.set_wait_secs opts wait))
> (with-configured-nimbus-connection nimbus
> (.killTopologyWithOpts nimbus name opts)
> (log-message "Killed topology: " name)
> )))
> {code}
> which in turn calls the following code in {{nimbus.clj}}:
> {code}
> ;; In: backtype.storm.daemon.nimbus
> (^void killTopologyWithOpts [this ^String storm-name ^KillOptions
> options]
> (check-storm-active! nimbus storm-name true)
> (let [topology-conf (try-read-storm-conf-from-name conf storm-name
> nimbus)]
> (check-authorization! nimbus storm-name topology-conf
> "killTopology"))
> (let [wait-amt (if (.is_set_wait_secs options)
> (.get_wait_secs options)
> )]
> (transition-name! nimbus storm-name [:kill wait-amt] true)
> ))
> {code}
> As you can see the current implementation does not pass success/failure
> information back to the caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (STORM-681) Auto insert license header with genthrift.sh
Kai Sasaki created STORM-681: Summary: Auto insert license header with genthrift.sh Key: STORM-681 URL: https://issues.apache.org/jira/browse/STORM-681 Project: Apache Storm Issue Type: Improvement Affects Versions: 0.10.0, 0.9.3-rc2 Reporter: Kai Sasaki Assignee: Kai Sasaki Priority: Minor Current genthrift.sh does not insert license headers into generated source codes. These java codes and python codes should have license headers. And documentation about this command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-671) Measure tuple serialization/deserialization latency.
[ https://issues.apache.org/jira/browse/STORM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-671: Assignee: Kai Sasaki > Measure tuple serialization/deserialization latency. > > > Key: STORM-671 > URL: https://issues.apache.org/jira/browse/STORM-671 > Project: Apache Storm > Issue Type: New Feature >Reporter: Robert Joseph Evans >Assignee: Kai Sasaki > > Some times the serialization/deserialization cost can be very high, and it is > not currently measured anywhere in storm. We should measure it, at least in > a similar way to how we do execute and process latency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-671) Measure tuple serialization/deserialization latency.
[ https://issues.apache.org/jira/browse/STORM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321928#comment-14321928 ] Kai Sasaki commented on STORM-671: -- [~revans2] Can I work on this issue? My understanding to this measurement is that each component save slowest serialization/deserialization time in TopologyInfo and user can lookup this metrics from ui view, right? > Measure tuple serialization/deserialization latency. > > > Key: STORM-671 > URL: https://issues.apache.org/jira/browse/STORM-671 > Project: Apache Storm > Issue Type: New Feature >Reporter: Robert Joseph Evans > > Some times the serialization/deserialization cost can be very high, and it is > not currently measured anywhere in storm. We should measure it, at least in > a similar way to how we do execute and process latency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-669) Replace links with ones to latest api document
[ https://issues.apache.org/jira/browse/STORM-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated STORM-669: - Priority: Minor (was: Major) > Replace links with ones to latest api document > -- > > Key: STORM-669 > URL: https://issues.apache.org/jira/browse/STORM-669 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.10.0, 0.9.3-rc2 >Reporter: Kai Sasaki >Assignee: Kai Sasaki >Priority: Minor > Labels: documentaion, javadoc > > Replace links to old api document with new ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-624) Some typos in SECURITY.md
[ https://issues.apache.org/jira/browse/STORM-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki resolved STORM-624. -- Resolution: Fixed Merged > Some typos in SECURITY.md > - > > Key: STORM-624 > URL: https://issues.apache.org/jira/browse/STORM-624 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Kai Sasaki >Assignee: Kai Sasaki >Priority: Trivial > Labels: documentaion > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (STORM-391) KafkaSpout to await for the topic
[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki closed STORM-391. Resolution: Won't Fix Migrated to STORM-650 > KafkaSpout to await for the topic > - > > Key: STORM-391 > URL: https://issues.apache.org/jira/browse/STORM-391 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.9.2-incubating >Reporter: Alexey Raga >Assignee: Kai Sasaki > Labels: features > > When topic does not yet exist and the consumer is asked to consume from it, > the default behaviour for Kafka heigh-level consumer is to "await" for the > topic without a failure. > KafkaSpout currently fails trying to get the partition information about the > topic that does not exist. > It may be a good idea to have the same common behaviour in KafkaSpout and it > can probably be implemented through the zookeeper watchers: if topic does not > exist, then set up a watcher and don't do anything until it yields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-669) Replace links with ones to latest api document
[ https://issues.apache.org/jira/browse/STORM-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated STORM-669: - Summary: Replace links with ones to latest api document (was: Replace links to latest api document) > Replace links with ones to latest api document > -- > > Key: STORM-669 > URL: https://issues.apache.org/jira/browse/STORM-669 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.10.0, 0.9.3-rc2 >Reporter: Kai Sasaki >Assignee: Kai Sasaki > Labels: documentaion, javadoc > > Replace links to old api document with new ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-669) Replace links to latest api document
Kai Sasaki created STORM-669: Summary: Replace links to latest api document Key: STORM-669 URL: https://issues.apache.org/jira/browse/STORM-669 Project: Apache Storm Issue Type: Improvement Affects Versions: 0.10.0, 0.9.3-rc2 Reporter: Kai Sasaki Assignee: Kai Sasaki Replace links to old api document with new ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-663) Create javadocs for BoltDeclarer
[ https://issues.apache.org/jira/browse/STORM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-663: Assignee: Kai Sasaki > Create javadocs for BoltDeclarer > > > Key: STORM-663 > URL: https://issues.apache.org/jira/browse/STORM-663 > Project: Apache Storm > Issue Type: Documentation >Affects Versions: 0.9.3 >Reporter: Karl Richter >Assignee: Kai Sasaki > > There's no documentation of grouping stream usage in the javadocs of > BoltDeclarerhttp://storm.apache.org/javadoc/apidocs/backtype/storm/topology/BoltDeclarer.html. > It might be sufficient to a links to sites or HTML anchors of the full text > documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-653) missing DRPC HTTP port in SECURITY.md
[ https://issues.apache.org/jira/browse/STORM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-653: Assignee: Kai Sasaki > missing DRPC HTTP port in SECURITY.md > - > > Key: STORM-653 > URL: https://issues.apache.org/jira/browse/STORM-653 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Kai Sasaki >Assignee: Kai Sasaki > Labels: documentaion, drpc > > There is no description about DRPC HTTP port in SECURITY.md. > This port is used by DRPC Client as default 3774 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-653) missing DRPC HTTP port in SECURITY.md
Kai Sasaki created STORM-653: Summary: missing DRPC HTTP port in SECURITY.md Key: STORM-653 URL: https://issues.apache.org/jira/browse/STORM-653 Project: Apache Storm Issue Type: Bug Affects Versions: 0.10.0 Reporter: Kai Sasaki There is no description about DRPC HTTP port in SECURITY.md. This port is used by DRPC Client as default 3774 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-590) KafkaSpout should use kafka consumer api
[ https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301025#comment-14301025 ] Kai Sasaki commented on STORM-590: -- [~parth.brahmbhatt] Of couse, it's ok to assign this ticket to you. When you submit refactored codes I want to check it. Thank you. > 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: Kai Sasaki > > 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] [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 ] Kai Sasaki updated STORM-590: - Assignee: Parth Brahmbhatt (was: Kai Sasaki) > 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] [Created] (STORM-639) storm-maven-plugin not found
Kai Sasaki created STORM-639: Summary: storm-maven-plugin not found Key: STORM-639 URL: https://issues.apache.org/jira/browse/STORM-639 Project: Apache Storm Issue Type: Bug Affects Versions: 0.10.0 Reporter: Kai Sasaki Assignee: Kai Sasaki Priority: Minor storm-maven-plugin is required by storm-core, but it cannot be found. ``` [ERROR] Error resolving version for plugin 'org.apache.storm:storm-maven-plugins' from the repositories [local (/Users/sasakikai/.m2/repository), central (https://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository -> [Help 1] org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for plugin 'org.apache.storm:storm-maven-plugins' from the repositories [local (/Users/sasakikai/.m2/repository), central (https://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository at org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.selectVersion(DefaultPluginVersionResolver.java:236) at org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.resolveFromRepository(DefaultPluginVersionResolver.java:148) at org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver.resolve(DefaultPluginVersionResolver.java:96) at org.apache.maven.lifecycle.internal.LifecyclePluginResolver.resolveMissingPluginVersions(LifecyclePluginResolver.java:71) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:135) at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:97) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:109) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. ``` This plugin should be installed in local repository before compile storm-core. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-596) "topology.receiver.buffer.size" has no effect
[ https://issues.apache.org/jira/browse/STORM-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297985#comment-14297985 ] Kai Sasaki commented on STORM-596: -- [~caofangkun] I'm so sorry. I missed this [post](http://qnalist.com/questions/5094095/topology-receiver-buffer-size-no-longer-honored) As you modified, I agree with you that these codes are no longer needed. > "topology.receiver.buffer.size" has no effect > -- > > Key: STORM-596 > URL: https://issues.apache.org/jira/browse/STORM-596 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 0.10.0, 0.9.3-rc2 >Reporter: caofangkun >Assignee: caofangkun >Priority: Minor > > https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/messaging/loader.clj#L27 > backtype.storm.messaging.loader#mk-receive-thread accepts max-buffer-size as > an input but the value isn't used within the function. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-630) Support for Clojure 1.6.0
[ https://issues.apache.org/jira/browse/STORM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-630: Assignee: Kai Sasaki > Support for Clojure 1.6.0 > - > > Key: STORM-630 > URL: https://issues.apache.org/jira/browse/STORM-630 > Project: Apache Storm > Issue Type: Bug >Reporter: Dave Kincaid >Assignee: Kai Sasaki > > Trying to use Storm under Clojure 1.6.0 causes errors with namespace > conflicts (specifically the function some?). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-629) Place Link to Source Code Repository on Webpage
[ https://issues.apache.org/jira/browse/STORM-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-629: Assignee: Kai Sasaki > Place Link to Source Code Repository on Webpage > --- > > Key: STORM-629 > URL: https://issues.apache.org/jira/browse/STORM-629 > Project: Apache Storm > Issue Type: Task >Reporter: Henning Kropp >Assignee: Kai Sasaki >Priority: Minor > > Maybe it just me, but I was unable to find a link to the source code > repository on the webpage. > Good places for that could be: > * http://storm.apache.org/downloads.html > * http://storm.apache.org/documentation/Contributing-to-Storm.html > * > http://storm.apache.org/documentation/Setting-up-development-environment.html > * http://storm.apache.org/about/free-and-open-source.html > I assume it is this one git://git.apache.org/incubator-storm.git ?? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-624) Some typos in SECURITY.md
[ https://issues.apache.org/jira/browse/STORM-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated STORM-624: - There are some typos in SECURITY.md > Some typos in SECURITY.md > - > > Key: STORM-624 > URL: https://issues.apache.org/jira/browse/STORM-624 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Kai Sasaki >Assignee: Kai Sasaki >Priority: Trivial > Labels: documentaion > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-624) Some typos in SECURITY.md
Kai Sasaki created STORM-624: Summary: Some typos in SECURITY.md Key: STORM-624 URL: https://issues.apache.org/jira/browse/STORM-624 Project: Apache Storm Issue Type: Bug Affects Versions: 0.10.0 Reporter: Kai Sasaki Assignee: Kai Sasaki Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-614) storm-core mvn artifacts dependencies are not downloaded automatically
[ https://issues.apache.org/jira/browse/STORM-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276151#comment-14276151 ] Kai Sasaki commented on STORM-614: -- It seems clojar repository has already been added in master branch. https://github.com/apache/storm/blob/master/pom.xml#L556-L565 There might be other problem if you cannot download dependencies yet. > storm-core mvn artifacts dependencies are not downloaded automatically > -- > > Key: STORM-614 > URL: https://issues.apache.org/jira/browse/STORM-614 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 0.9.3 > Environment: Gradle 2.1 java project >Reporter: Nikolai Korshunov >Priority: Minor > Labels: maven, newbie > > I added 'storm-core' artefact to my gradle project. Gradle couldn't download > roughly half of artefact dependencies (clj-time, ring-servlet and others), > because it couldn't find them. pom.xml of 'storm-core' doesn't contain any > links to any external repos. > Problem is: these dependencies are stored in 'clojars' repo, and during build > of all storm, dependent projects use links from root pom.xml, and thus when > 'storm-core' artefact is deployed to maven central it is broken by default. > Suggestions to solving are: > 1) Update documentation on storm.apache.org (in Downloads section) > 2) Adding 'clojars' repo url to 'storm-core' pom.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-623) Generate latest javadocs
[ https://issues.apache.org/jira/browse/STORM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated STORM-623: - Affects Version/s: (was: 0.9.3-rc2) 0.10.0 0.9.3 > Generate latest javadocs > > > Key: STORM-623 > URL: https://issues.apache.org/jira/browse/STORM-623 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.9.3, 0.10.0 >Reporter: Kai Sasaki >Assignee: Kai Sasaki > Labels: documentaion, javadoc > > There is no latest javadoc on official site now. > https://storm.apache.org/documentation/Home.html > In addition to this, current javadocs are hosted outside of apache domain. > Maven build pipeline includes generation process of javadoc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-623) Generate latest javadocs
Kai Sasaki created STORM-623: Summary: Generate latest javadocs Key: STORM-623 URL: https://issues.apache.org/jira/browse/STORM-623 Project: Apache Storm Issue Type: Improvement Affects Versions: 0.9.3-rc2 Reporter: Kai Sasaki Assignee: Kai Sasaki There is no latest javadoc on official site now. https://storm.apache.org/documentation/Home.html In addition to this, current javadocs are hosted outside of apache domain. Maven build pipeline includes generation process of javadoc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-620) Duplicate maven plugin declaration
Kai Sasaki created STORM-620: Summary: Duplicate maven plugin declaration Key: STORM-620 URL: https://issues.apache.org/jira/browse/STORM-620 Project: Apache Storm Issue Type: Bug Affects Versions: 0.9.3-rc2 Reporter: Kai Sasaki Assignee: Kai Sasaki Priority: Trivial maven-javadoc-plugin is included reporting section in pom.xml doubly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-590) KafkaSpout should use kafka consumer api
Kai Sasaki created STORM-590: Summary: 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: Kai Sasaki 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-391) KafkaSpout to await for the topic
[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-391: Assignee: Kai Sasaki > KafkaSpout to await for the topic > - > > Key: STORM-391 > URL: https://issues.apache.org/jira/browse/STORM-391 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.9.2-incubating >Reporter: Alexey Raga >Assignee: Kai Sasaki > Labels: features > > When topic does not yet exist and the consumer is asked to consume from it, > the default behaviour for Kafka heigh-level consumer is to "await" for the > topic without a failure. > KafkaSpout currently fails trying to get the partition information about the > topic that does not exist. > It may be a good idea to have the same common behaviour in KafkaSpout and it > can probably be implemented through the zookeeper watchers: if topic does not > exist, then set up a watcher and don't do anything until it yields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (STORM-391) KafkaSpout to await for the topic
[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233722#comment-14233722 ] Kai Sasaki commented on STORM-391: -- [~sriharsha] I'm implementing this option with a event watcher for ZK now. I'll send PR for this patch. Then please review it. > KafkaSpout to await for the topic > - > > Key: STORM-391 > URL: https://issues.apache.org/jira/browse/STORM-391 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.9.2-incubating >Reporter: Alexey Raga > Labels: features > > When topic does not yet exist and the consumer is asked to consume from it, > the default behaviour for Kafka heigh-level consumer is to "await" for the > topic without a failure. > KafkaSpout currently fails trying to get the partition information about the > topic that does not exist. > It may be a good idea to have the same common behaviour in KafkaSpout and it > can probably be implemented through the zookeeper watchers: if topic does not > exist, then set up a watcher and don't do anything until it yields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-391) KafkaSpout to await for the topic
[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated STORM-391: - Assignee: (was: Kai Sasaki) > KafkaSpout to await for the topic > - > > Key: STORM-391 > URL: https://issues.apache.org/jira/browse/STORM-391 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.9.2-incubating >Reporter: Alexey Raga > Labels: features > > When topic does not yet exist and the consumer is asked to consume from it, > the default behaviour for Kafka heigh-level consumer is to "await" for the > topic without a failure. > KafkaSpout currently fails trying to get the partition information about the > topic that does not exist. > It may be a good idea to have the same common behaviour in KafkaSpout and it > can probably be implemented through the zookeeper watchers: if topic does not > exist, then set up a watcher and don't do anything until it yields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (STORM-391) KafkaSpout to await for the topic
[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki reassigned STORM-391: Assignee: Kai Sasaki > KafkaSpout to await for the topic > - > > Key: STORM-391 > URL: https://issues.apache.org/jira/browse/STORM-391 > Project: Apache Storm > Issue Type: Improvement >Affects Versions: 0.9.2-incubating >Reporter: Alexey Raga >Assignee: Kai Sasaki > Labels: features > > When topic does not yet exist and the consumer is asked to consume from it, > the default behaviour for Kafka heigh-level consumer is to "await" for the > topic without a failure. > KafkaSpout currently fails trying to get the partition information about the > topic that does not exist. > It may be a good idea to have the same common behaviour in KafkaSpout and it > can probably be implemented through the zookeeper watchers: if topic does not > exist, then set up a watcher and don't do anything until it yields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (STORM-574) Typo in storm-kafka README
[ https://issues.apache.org/jira/browse/STORM-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki resolved STORM-574. -- Resolution: Fixed Merged https://github.com/apache/storm/pull/320 > Typo in storm-kafka README > -- > > Key: STORM-574 > URL: https://issues.apache.org/jira/browse/STORM-574 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 0.9.2-incubating >Reporter: Kai Sasaki >Assignee: Kai Sasaki >Priority: Trivial > > Fix some typos in storm-kafka README > https://github.com/apache/storm/pull/320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (STORM-574) Typo in storm-kafka README
[ https://issues.apache.org/jira/browse/STORM-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated STORM-574: - Summary: Typo in storm-kafka README (was: Type in storm-kafka README) > Typo in storm-kafka README > -- > > Key: STORM-574 > URL: https://issues.apache.org/jira/browse/STORM-574 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka >Affects Versions: 0.9.2-incubating >Reporter: Kai Sasaki >Assignee: Kai Sasaki >Priority: Trivial > > Fix some typos in storm-kafka README > https://github.com/apache/storm/pull/320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (STORM-574) Type in storm-kafka README
Kai Sasaki created STORM-574: Summary: Type in storm-kafka README Key: STORM-574 URL: https://issues.apache.org/jira/browse/STORM-574 Project: Apache Storm Issue Type: Bug Components: storm-kafka Affects Versions: 0.9.2-incubating Reporter: Kai Sasaki Assignee: Kai Sasaki Priority: Trivial Fix some typos in storm-kafka README https://github.com/apache/storm/pull/320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
