[jira] [Updated] (STORM-3253) Deprecate 'storm repl' subcommand
[ https://issues.apache.org/jira/browse/STORM-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3253: -- Labels: java-migration pull-request-available (was: java-migration) > Deprecate 'storm repl' subcommand > - > > Key: STORM-3253 > URL: https://issues.apache.org/jira/browse/STORM-3253 > Project: Apache Storm > Issue Type: Task > Components: storm-core >Reporter: Derek Dagit >Assignee: Derek Dagit >Priority: Major > Labels: java-migration, pull-request-available > > We should deprecate {{storm repl}} so that we can remove it in a future > release. > We would remove it because of the move away from Clojure toward Java. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (STORM-3253) Deprecate 'storm repl' subcommand
[ https://issues.apache.org/jira/browse/STORM-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Dagit reassigned STORM-3253: -- Assignee: Derek Dagit > Deprecate 'storm repl' subcommand > - > > Key: STORM-3253 > URL: https://issues.apache.org/jira/browse/STORM-3253 > Project: Apache Storm > Issue Type: Task > Components: storm-core >Reporter: Derek Dagit >Assignee: Derek Dagit >Priority: Major > Labels: java-migration > > We should deprecate {{storm repl}} so that we can remove it in a future > release. > We would remove it because of the move away from Clojure toward Java. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (STORM-3253) Deprecate 'storm repl' subcommand
Derek Dagit created STORM-3253: -- Summary: Deprecate 'storm repl' subcommand Key: STORM-3253 URL: https://issues.apache.org/jira/browse/STORM-3253 Project: Apache Storm Issue Type: Task Components: storm-core Reporter: Derek Dagit We should deprecate {{storm repl}} so that we can remove it in a future release. We would remove it because of the move away from Clojure toward Java. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3243) Clean up Maven POM dependency on clojure
[ https://issues.apache.org/jira/browse/STORM-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3243: -- Labels: java-migration jstorm-merger pull-request-available (was: java-migration jstorm-merger) > Clean up Maven POM dependency on clojure > > > Key: STORM-3243 > URL: https://issues.apache.org/jira/browse/STORM-3243 > Project: Apache Storm > Issue Type: Improvement > Components: build >Reporter: Derek Dagit >Assignee: Derek Dagit >Priority: Major > Labels: java-migration, jstorm-merger, pull-request-available > > Investigate whether we can drop non-test dependencies on Clojure. Drop > dependencies on Clojure that we no longer need. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (STORM-515) Clojure documentation and examples
[ https://issues.apache.org/jira/browse/STORM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Dagit reassigned STORM-515: - Assignee: Dmitri Sotnikov > Clojure documentation and examples > -- > > Key: STORM-515 > URL: https://issues.apache.org/jira/browse/STORM-515 > Project: Apache Storm > Issue Type: Improvement > Components: documentation, examples >Affects Versions: 0.9.2-incubating >Reporter: Dmitri Sotnikov >Assignee: Dmitri Sotnikov >Priority: Major > Labels: newbie > Fix For: 2.0.0 > > > Clojure storm-starter example is extremely basic > (https://github.com/apache/storm/blob/master/examples/storm-starter/src/clj/storm/starter/clj/word_count.clj) > and doesn't demonstrate many use cases. > Clojure documentation page > (http://storm.incubator.apache.org/documentation/Clojure-DSL.html) has > unreadable code samples, and glosses over many details in how bolts are > setup, how to initialize parametarized bolts, where the requires such as > execute come from, and so on. > It would be nice to see clear documentation with properly documented examples > for each of the use cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-515) Clojure documentation and examples
[ https://issues.apache.org/jira/browse/STORM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Dagit resolved STORM-515. --- Resolution: Fixed Fix Version/s: 2.0.0 Closing this as the code has been merged already. Thanks [~yogthos]. > Clojure documentation and examples > -- > > Key: STORM-515 > URL: https://issues.apache.org/jira/browse/STORM-515 > Project: Apache Storm > Issue Type: Improvement > Components: documentation, examples >Affects Versions: 0.9.2-incubating >Reporter: Dmitri Sotnikov >Priority: Major > Labels: newbie > Fix For: 2.0.0 > > > Clojure storm-starter example is extremely basic > (https://github.com/apache/storm/blob/master/examples/storm-starter/src/clj/storm/starter/clj/word_count.clj) > and doesn't demonstrate many use cases. > Clojure documentation page > (http://storm.incubator.apache.org/documentation/Clojure-DSL.html) has > unreadable code samples, and glosses over many details in how bolts are > setup, how to initialize parametarized bolts, where the requires such as > execute come from, and so on. > It would be nice to see clear documentation with properly documented examples > for each of the use cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3251) Using Logviewer Filter settings causes anyone to access logs via log viewer REST API
[ https://issues.apache.org/jira/browse/STORM-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3251: -- Labels: pull-request-available (was: ) > Using Logviewer Filter settings causes anyone to access logs via log viewer > REST API > > > Key: STORM-3251 > URL: https://issues.apache.org/jira/browse/STORM-3251 > Project: Apache Storm > Issue Type: Bug >Reporter: Aaron Gresch >Assignee: Aaron Gresch >Priority: Critical > Labels: pull-request-available > > The rest API for logviewer access is checking if UI filter params is set to > deny access to users. It's possible now to configure the logviewer without > UI filter params, so this check is no longer sufficient and can allow anyone > access to logs. > > See ResourceAuthorizer line 68 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3252) Blobstore sync bug fix
[ https://issues.apache.org/jira/browse/STORM-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3252: -- Labels: pull-request-available (was: ) > Blobstore sync bug fix > -- > > Key: STORM-3252 > URL: https://issues.apache.org/jira/browse/STORM-3252 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.2.2 >Reporter: Arun Mahadevan >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0, 1.x > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3252) Blobstore sync bug fix
[ https://issues.apache.org/jira/browse/STORM-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Mahadevan updated STORM-3252: -- Issue Type: Bug (was: Improvement) > Blobstore sync bug fix > -- > > Key: STORM-3252 > URL: https://issues.apache.org/jira/browse/STORM-3252 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 1.2.2 >Reporter: Arun Mahadevan >Priority: Major > Fix For: 2.0.0, 1.x > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (STORM-3252) Blobstore sync bug fix
Arun Mahadevan created STORM-3252: - Summary: Blobstore sync bug fix Key: STORM-3252 URL: https://issues.apache.org/jira/browse/STORM-3252 Project: Apache Storm Issue Type: Improvement Affects Versions: 1.2.2 Reporter: Arun Mahadevan Fix For: 2.0.0, 1.x -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3251) Using Logviewer Filter settings causes anyone to access logs via log viewer REST API
[ https://issues.apache.org/jira/browse/STORM-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Gresch updated STORM-3251: Description: The rest API for logviewer access is checking if UI filter params is set to deny access to users. It's possible now to configure the logviewer without UI filter params, so this check is no longer sufficient and can allow anyone access to logs. See ResourceAuthorizer line 68 was:The rest API for logviewer access is checking if UI filter params is set to deny access to users. It's possible now to configure the logviewer without UI filter params, so this check is no longer sufficient and can allow anyone access to logs. > Using Logviewer Filter settings causes anyone to access logs via log viewer > REST API > > > Key: STORM-3251 > URL: https://issues.apache.org/jira/browse/STORM-3251 > Project: Apache Storm > Issue Type: Bug >Reporter: Aaron Gresch >Assignee: Aaron Gresch >Priority: Critical > > The rest API for logviewer access is checking if UI filter params is set to > deny access to users. It's possible now to configure the logviewer without > UI filter params, so this check is no longer sufficient and can allow anyone > access to logs. > > See ResourceAuthorizer line 68 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (STORM-3251) Using Logviewer Filter settings causes anyone to access logs via log viewer REST API
Aaron Gresch created STORM-3251: --- Summary: Using Logviewer Filter settings causes anyone to access logs via log viewer REST API Key: STORM-3251 URL: https://issues.apache.org/jira/browse/STORM-3251 Project: Apache Storm Issue Type: Bug Reporter: Aaron Gresch Assignee: Aaron Gresch The rest API for logviewer access is checking if UI filter params is set to deny access to users. It's possible now to configure the logviewer without UI filter params, so this check is no longer sufficient and can allow anyone access to logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (STORM-3233) Upgrade zookeeper client to newest version (3.4.13)
[ https://issues.apache.org/jira/browse/STORM-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reopened STORM-3233: Need to revert this so we can wait for 3.4.14 > Upgrade zookeeper client to newest version (3.4.13) > --- > > Key: STORM-3233 > URL: https://issues.apache.org/jira/browse/STORM-3233 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core >Affects Versions: 2.0.0 >Reporter: Michal Koziorowski >Assignee: Michal Koziorowski >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0, 1.2.3, 1.1.4 > > Time Spent: 1h > Remaining Estimate: 0h > > Hi, > I would like to see new zookeeper client (3.4.13) used in storm. > New release contains an important fix for cloud environments where zookeeper > servers have dynamic ips > ([https://jira.apache.org/jira/browse/ZOOKEEPER-2184]). > If possible, it would be nice to see updated zookeeper also on older storm > versions (1.2.x, 1.1.x) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3233) Upgrade zookeeper client to newest version (3.4.13)
[ https://issues.apache.org/jira/browse/STORM-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated STORM-3233: --- Summary: Upgrade zookeeper client to newest version (3.4.13) (was: Upgrade zookeeper client to newest version (3.4.14)) > Upgrade zookeeper client to newest version (3.4.13) > --- > > Key: STORM-3233 > URL: https://issues.apache.org/jira/browse/STORM-3233 > Project: Apache Storm > Issue Type: New Feature > Components: storm-core >Affects Versions: 2.0.0 >Reporter: Michal Koziorowski >Assignee: Michal Koziorowski >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0, 1.2.3, 1.1.4 > > Time Spent: 1h > Remaining Estimate: 0h > > Hi, > I would like to see new zookeeper client (3.4.13) used in storm. > New release contains an important fix for cloud environments where zookeeper > servers have dynamic ips > ([https://jira.apache.org/jira/browse/ZOOKEEPER-2184]). > If possible, it would be nice to see updated zookeeper also on older storm > versions (1.2.x, 1.1.x) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3249) Nimbus Shutdown Faster
[ https://issues.apache.org/jira/browse/STORM-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3249. Resolution: Fixed Fix Version/s: 2.0.1 > Nimbus Shutdown Faster > -- > > Key: STORM-3249 > URL: https://issues.apache.org/jira/browse/STORM-3249 > Project: Apache Storm > Issue Type: Bug > Components: storm-server >Affects Versions: 2.0.0 >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Major > Labels: pull-request-available > Fix For: 2.0.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Nimbus takes for ever to shut down in 2.x. It would really be nice to fix > that. (and it is really our own fault why it takes so long) -- This message was sent by Atlassian JIRA (v7.6.3#76005)