[jira] [Commented] (STORM-1728) TransactionalTridentKafkaSpout error

[ https://issues.apache.org/jira/browse/STORM-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294669#comment-15294669 ] ASF GitHub Bot commented on STORM-1728: --- Github user lerouxrgd closed the pull request at:

[GitHub] storm pull request: fix for PartitionedTridentSpoutExecutor STORM-...

Github user lerouxrgd closed the pull request at: https://github.com/apache/storm/pull/1438 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (STORM-1858) improve KafkaBolt performance

Xin Wang created STORM-1858: --- Summary: improve KafkaBolt performance Key: STORM-1858 URL: https://issues.apache.org/jira/browse/STORM-1858 Project: Apache Storm Issue Type: Improvement

[jira] [Commented] (STORM-1727) document 1.0 package renaming and how to use the migration tool

[ https://issues.apache.org/jira/browse/STORM-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294629#comment-15294629 ] ASF GitHub Bot commented on STORM-1727: --- Github user vesense commented on the pull request:

[GitHub] storm pull request: STORM-1727: add storm 1.0.0 rename note

Github user vesense commented on the pull request: https://github.com/apache/storm/pull/1358#issuecomment-220751894 @ptgoetz Seems like this change should be published to the storm web site. --- If your project is set up for it, you can reply to this email and have your reply appear

[jira] [Updated] (STORM-1857) HDFS Topologies should support config parameters from a YAML file

[ https://issues.apache.org/jira/browse/STORM-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sivaguru Kannan updated STORM-1857: --- Description: HDFS test topologies should support specifying a yaml file for passing in config

[jira] [Updated] (STORM-1857) HDFS Topologies should support config parameters from a YAML file

[ https://issues.apache.org/jira/browse/STORM-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sivaguru Kannan updated STORM-1857: --- Summary: HDFS Topologies should support config parameters from a YAML file (was: HDFS test

[jira] [Commented] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294320#comment-15294320 ] ASF GitHub Bot commented on STORM-1674: --- Github user moesol commented on the pull request:

[GitHub] storm pull request: (STORM-1674) Idle KafkaSpout consumes more ban...

Github user moesol commented on the pull request: https://github.com/apache/storm/pull/1393#issuecomment-220727660 I think it's awesome that this change is getting in! I'll be looking out for the next release that contains this PR. Robert Hastings, Lab SDL: 619-553-0826,

Re: Storm's use of ASF Parent POM (FW: [ANN] Apache Software Foundation Parent POM Version 18 Released)

One of the more important things the ASF parent POM does is setup the maven release plugin for releasing the necessary artifacts to repository.a.o. So in your testing, you should test the maven release plugin, preferably with the “dry run” option so you don’t actually stage a release. :)

Re: Regarding types of DataPoint value for Metrics Consumer

+1 I agree. I think we have been considering that the clojure migration/JStorm merge would become 2.0. Maybe we should reconsider that in order to allow major version bumps and closer adherence to semantic versioning. I can also think of a few areas where I’d like to see some

Re: Is something wrong with this specifications ?

i found this in worker log file unable to reconnect to ZooKeeper service, session 0x154cebecd950005 has expired, closing socket connection o.a.s.c.f.s.ConnectionStateManager [INFO] State change: LOST b.s.cluster [WARN] Received event :expired::none: with disconnected Zookeeper. On Fri, May 20,

[jira] [Created] (STORM-1857) HDFS test topologies should write to /tmp

Sivaguru Kannan created STORM-1857: -- Summary: HDFS test topologies should write to /tmp Key: STORM-1857 URL: https://issues.apache.org/jira/browse/STORM-1857 Project: Apache Storm Issue

Re: Is something wrong with this specifications ?

is there any help ? i'm still having this problem i submitted topology in local mode and worked fine but when i tried to submit it in distributed i got this Exception in thread "main" DRPCExecutionException(msg:Request timed out) On Sun, May 15, 2016 at 10:19 PM, sam mohel

[jira] [Updated] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1674: --- Affects Version/s: 1.0.1 0.10.1 > Idle KafkaSpout consumes more

[jira] [Resolved] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1674. Resolution: Fixed Fix Version/s: 1.1.0 1.0.2

[jira] [Closed] (STORM-1854) Trident transactional spouts are broken in 1.0.x

[ https://issues.apache.org/jira/browse/STORM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Morrigan Jones closed STORM-1854. - Resolution: Duplicate > Trident transactional spouts are broken in 1.0.x >

[jira] [Commented] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294081#comment-15294081 ] ASF GitHub Bot commented on STORM-1674: --- Github user ptgoetz commented on the pull request:

[jira] [Commented] (STORM-1854) Trident transactional spouts are broken in 1.0.x

[ https://issues.apache.org/jira/browse/STORM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294082#comment-15294082 ] Morrigan Jones commented on STORM-1854: --- Looks like this is a duplicate of

[GitHub] storm pull request: (STORM-1674) Idle KafkaSpout consumes more ban...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1393#issuecomment-220705013 Thanks @moesol I merged this into master, 1.x-branch and 1.0.x-branch. Note that with 1.0.x-branch this created a conflict, as `KafkaConfig.minFetchByte` had

[GitHub] storm pull request: STORM-1850: State Checkpointing Documentation ...

Github user omallassi closed the pull request at: https://github.com/apache/storm/pull/1433 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (STORM-1850) State Checkpointing documentation update regarding spout state management

[ https://issues.apache.org/jira/browse/STORM-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294059#comment-15294059 ] ASF GitHub Bot commented on STORM-1850: --- Github user omallassi closed the pull request at:

[jira] [Commented] (STORM-1850) State Checkpointing documentation update regarding spout state management

[ https://issues.apache.org/jira/browse/STORM-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294060#comment-15294060 ] ASF GitHub Bot commented on STORM-1850: --- GitHub user omallassi reopened a pull request:

[GitHub] storm pull request: STORM-1850: State Checkpointing Documentation ...

GitHub user omallassi reopened a pull request: https://github.com/apache/storm/pull/1433 STORM-1850: State Checkpointing Documentation update update the documentation following this discussion

[jira] [Commented] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294052#comment-15294052 ] ASF GitHub Bot commented on STORM-1674: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request: (STORM-1674) Idle KafkaSpout consumes more ban...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1393 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (STORM-1841) Address a few minor issues in windowing and doc

[ https://issues.apache.org/jira/browse/STORM-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294011#comment-15294011 ] Arun Mahadevan commented on STORM-1841: --- Thanks [~raghavgautam] for finding and reporting this

[jira] [Commented] (STORM-1853) Deserialization issues in Utils.javaDeserialize()

[ https://issues.apache.org/jira/browse/STORM-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294002#comment-15294002 ] ASF GitHub Bot commented on STORM-1853: --- GitHub user abhishekagarwal87 opened a pull request:

[GitHub] storm pull request: STORM-1853: Replace ClassLoaderObjectInputStre...

GitHub user abhishekagarwal87 opened a pull request: https://github.com/apache/storm/pull/1440 STORM-1853: Replace ClassLoaderObjectInputStream with ObjectInputStream You can merge this pull request into a Git repository by running: $ git pull

[GitHub] storm pull request: (STORM-1674) Idle KafkaSpout consumes more ban...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1393#issuecomment-220692188 I'm in the process of merging this. Other committers please hold off. More info to follow... --- If your project is set up for it, you can reply to this email and have

[jira] [Commented] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293987#comment-15293987 ] ASF GitHub Bot commented on STORM-1674: --- Github user ptgoetz commented on the pull request:

[jira] [Commented] (STORM-1674) Idle KafkaSpout consumes more bandwidth than needed

[ https://issues.apache.org/jira/browse/STORM-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293928#comment-15293928 ] ASF GitHub Bot commented on STORM-1674: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: (STORM-1674) Idle KafkaSpout consumes more ban...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1393#issuecomment-220683696 +1 Nice catch! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] storm pull request: FluxShellBolt/FluxShellSpout can now emit into...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1426#issuecomment-220682954 +1 @Darkless012 No worries on the branch for this. A committer will merge it into the appropriate branches. --- If your project is set up for it, you can

[GitHub] storm pull request: Add mvn versions note to DEVELOPER

GitHub user dossett opened a pull request: https://github.com/apache/storm/pull/1439 Add mvn versions note to DEVELOPER You can merge this pull request into a Git repository by running: $ git pull https://github.com/dossett/storm bump Alternatively you can review and apply

[jira] [Resolved] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1842. Resolution: Fixed > Forward references in storm.thrift cause tooling issues >

[jira] [Updated] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1842: --- Affects Version/s: 1.0.1 Fix Version/s: 1.1.0 1.0.2

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293888#comment-15293888 ] ASF GitHub Bot commented on STORM-1842: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-1842 (1.0.x) Forward references in storm...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1425 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293887#comment-15293887 ] ASF GitHub Bot commented on STORM-1842: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-1842 (1.x) Forward references in storm.t...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1424 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293880#comment-15293880 ] ASF GitHub Bot commented on STORM-1842: --- Github user ptgoetz commented on the pull request:

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293879#comment-15293879 ] ASF GitHub Bot commented on STORM-1842: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: STORM-1842 Forward references in storm.thrift ...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1423#issuecomment-220677726 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[GitHub] storm pull request: STORM-1842 (1.0.x) Forward references in storm...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1425#issuecomment-220677854 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[jira] [Commented] (STORM-1842) Forward references in storm.thrift cause tooling issues

[ https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293878#comment-15293878 ] ASF GitHub Bot commented on STORM-1842: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: STORM-1842 (1.x) Forward references in storm.t...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1424#issuecomment-220677791 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[GitHub] storm pull request: Bump version to 1.1.0-SNAPSHOT

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1432 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] storm pull request: Bump version to 1.1.0-SNAPSHOT

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1432#issuecomment-220676804 Thanks @HeartSaVioR. Merged. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

Storm's use of ASF Parent POM (FW: [ANN] Apache Software Foundation Parent POM Version 18 Released)

I see that Storm is using version 10 of this parent pom (https://github.com/apache/storm/blob/master/pom.xml#L21-L25). I will try upgrading to 18, mostly as a learning exercise since I¹m unfamiliar with what this does, unless anyone is aware of an obvious not to bother. Thanks! -Aaron On

Re: Merging to Multiple Branches

Is there a best practice for merging a PR to multiple branches? I have struggled with that in the past, probably due to shortcomings in my knowledge of git. I¹d be happy to aggregate suggestions and put them on the Developer page. Thanks! On 5/20/16, 12:08 PM, "P. Taylor Goetz"

[jira] [Updated] (STORM-1771) HiveState should flushAndClose before closing old or idle Hive connections

[ https://issues.apache.org/jira/browse/STORM-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-1771: -- Fix Version/s: 1.1.0 1.0.2 > HiveState should flushAndClose

[jira] [Updated] (STORM-1745) Add partition to PartitionManager logs where it's missing

[ https://issues.apache.org/jira/browse/STORM-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1745: --- Fix Version/s: 1.1.0 > Add partition to PartitionManager logs where it's missing >

[jira] [Updated] (STORM-1705) Cap on number of retries for a failed message in kafka spout

[ https://issues.apache.org/jira/browse/STORM-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Agarwal updated STORM-1705: It is not a bug but still want to be included in 1.0.2 release. > Cap on number of retries

[jira] [Updated] (STORM-1735) Nimbus logs that replication was not reached when min-replication-count was reached exactly

[ https://issues.apache.org/jira/browse/STORM-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1735: --- Fix Version/s: 1.1.0 > Nimbus logs that replication was not reached when

[jira] [Updated] (STORM-1749) Fix storm-starter links in the github code

[ https://issues.apache.org/jira/browse/STORM-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1749: --- Fix Version/s: (was: 1.0.1) 1.1.0 1.0.2 > Fix

[jira] [Updated] (STORM-1764) Pacemaker is throwing some stack traces

[ https://issues.apache.org/jira/browse/STORM-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1764: --- Fix Version/s: 1.1.0 > Pacemaker is throwing some stack traces >

[jira] [Updated] (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 ] P. Taylor Goetz updated STORM-1761: --- Fix Version/s: 1.1.0 > Storm-Solr Example Throws ArrayIndexOutOfBoundsException in Remote

[jira] [Updated] (STORM-1756) Storm-kafka tests leak resources due to retained references to KafkaServer

[ https://issues.apache.org/jira/browse/STORM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1756: --- Fix Version/s: 1.1.0 > Storm-kafka tests leak resources due to retained references to

[jira] [Updated] (STORM-1750) Report-error-and-die may not kill the worker

[ https://issues.apache.org/jira/browse/STORM-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1750: --- Fix Version/s: 1.1.0 > Report-error-and-die may not kill the worker >

[jira] [Updated] (STORM-1715) Jedis Default Host

[ https://issues.apache.org/jira/browse/STORM-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1715: --- Fix Version/s: (was: 1.0.1) 1.1.0 1.0.2 > Jedis

[jira] [Updated] (STORM-1713) Don't use proprietary NotImplementedException in storm-kafka

[ https://issues.apache.org/jira/browse/STORM-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1713: --- Fix Version/s: 1.1.0 > Don't use proprietary NotImplementedException in storm-kafka >

[jira] [Updated] (STORM-1678) abstract batch processing to common api `BatchHelper`

[ https://issues.apache.org/jira/browse/STORM-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1678: --- Fix Version/s: 1.1.0 > abstract batch processing to common api `BatchHelper` >

[jira] [Updated] (STORM-1661) Introduce a config to turn off blobstore acl validation in insecure mode

[ https://issues.apache.org/jira/browse/STORM-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1661: --- Fix Version/s: 1.1.0 > Introduce a config to turn off blobstore acl validation in insecure

Merging to Multiple Branches

Committers, when merging patches to multiple branches please make a note either in the associated JIRA or pull request (which will get mirrored to JIRA) which branches it was merged to. This makes tracking which branches a patch landed in a lot easier. I think most of us are in the habit of

[jira] [Resolved] (STORM-1164) Code cleanup for typos, warnings and conciseness

[ https://issues.apache.org/jira/browse/STORM-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved STORM-1164. --- Resolution: Fixed > Code cleanup for typos, warnings and conciseness >

[jira] [Resolved] (STORM-1352) Trident should support writing to multiple Kafka clusters

[ https://issues.apache.org/jira/browse/STORM-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved STORM-1352. --- Resolution: Fixed > Trident should support writing to multiple Kafka clusters

[jira] [Updated] (STORM-1352) Trident should support writing to multiple Kafka clusters

[ https://issues.apache.org/jira/browse/STORM-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-1352: -- Fix Version/s: 1.0.0 > Trident should support writing to multiple Kafka

[jira] [Updated] (STORM-1164) Code cleanup for typos, warnings and conciseness

[ https://issues.apache.org/jira/browse/STORM-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-1164: -- Fix Version/s: 1.0.0 > Code cleanup for typos, warnings and conciseness >

[jira] [Updated] (STORM-1835) add lock info in thread dump

[ https://issues.apache.org/jira/browse/STORM-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1835: --- Fix Version/s: 1.1.0 > add lock info in thread dump > > >

[jira] [Commented] (STORM-1728) TransactionalTridentKafkaSpout error

[ https://issues.apache.org/jira/browse/STORM-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293674#comment-15293674 ] ASF GitHub Bot commented on STORM-1728: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: fix for PartitionedTridentSpoutExecutor STORM-...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1438#issuecomment-220656428 @lerouxrgd Thanks for the patch, but this looks like a duplicate of #1429 which is eligible for merge. Would you mind closing this PR? The earlier PR was raised

[GitHub] storm pull request: Bump version to 1.1.0-SNAPSHOT

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1432#issuecomment-22063 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[jira] [Updated] (STORM-1728) TransactionalTridentKafkaSpout error

[ https://issues.apache.org/jira/browse/STORM-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1728: --- Fix Version/s: 1.1.0 1.0.2 > TransactionalTridentKafkaSpout error >

[jira] [Created] (STORM-1856) Release Apache Storm 1.1.0

P. Taylor Goetz created STORM-1856: -- Summary: Release Apache Storm 1.1.0 Key: STORM-1856 URL: https://issues.apache.org/jira/browse/STORM-1856 Project: Apache Storm Issue Type: Epic

[jira] [Created] (STORM-1855) Release Apache Storm 1.0.2

P. Taylor Goetz created STORM-1855: -- Summary: Release Apache Storm 1.0.2 Key: STORM-1855 URL: https://issues.apache.org/jira/browse/STORM-1855 Project: Apache Storm Issue Type: Epic

[jira] [Resolved] (STORM-1721) Release Apache Storm 1.0.1

[ https://issues.apache.org/jira/browse/STORM-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1721. Resolution: Fixed > Release Apache Storm 1.0.1 > -- > >

[jira] [Commented] (STORM-1728) TransactionalTridentKafkaSpout error

[ https://issues.apache.org/jira/browse/STORM-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293634#comment-15293634 ] ASF GitHub Bot commented on STORM-1728: --- GitHub user lerouxrgd opened a pull request:

[GitHub] storm pull request: fix for PartitionedTridentSpoutExecutor STORM-...

GitHub user lerouxrgd opened a pull request: https://github.com/apache/storm/pull/1438 fix for PartitionedTridentSpoutExecutor STORM-1728 UT passed locally for storm-core and storm-kafka. Also tested in a dev setup (Storm and Kafka running locally). You can merge this pull

[GitHub] storm pull request: Ack late tuples in windowed mode

GitHub user kosii opened a pull request: https://github.com/apache/storm/pull/1437 Ack late tuples in windowed mode The current implementation simply ignores late tuples without acking them, which causes timeouts and replays after TOPOLOGY_MESSAGE_TIMEOUT_SECS. A tuple which

[jira] [Updated] (STORM-1854) Trident transactional spouts are broken in 1.0.x

[ https://issues.apache.org/jira/browse/STORM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Morrigan Jones updated STORM-1854: -- Description: In the process of upgrading our Storm code from 0.10.0 to 1.0.0, I've run into an

[jira] [Created] (STORM-1854) Trident transactional spouts are broken in 1.0.x

Morrigan Jones created STORM-1854: - Summary: Trident transactional spouts are broken in 1.0.x Key: STORM-1854 URL: https://issues.apache.org/jira/browse/STORM-1854 Project: Apache Storm

Re: Regarding types of DataPoint value for Metrics Consumer

Yes, so what I would propose is... If we add in a new dependency to the storm lib directory that is not shaded, or decide to stop shading a dependency it should at least be a minor version bump, but I would prefer a major version bump (potentially binary incompatible change).If we bump a

[jira] [Commented] (STORM-1832) Consistently slow metrics consumer triggers backpressure which will be never back to normal

[ https://issues.apache.org/jira/browse/STORM-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293338#comment-15293338 ] Michael Schonfeld commented on STORM-1832: -- Lately, my topologies have gotten stuck on

[jira] [Created] (STORM-1853) Deserialization issues in Utils.javaDeserialize()

Abhishek Agarwal created STORM-1853: --- Summary: Deserialization issues in Utils.javaDeserialize() Key: STORM-1853 URL: https://issues.apache.org/jira/browse/STORM-1853 Project: Apache Storm

[jira] [Commented] (STORM-1475) storm-elasticsearch should support ES 2.X

[ https://issues.apache.org/jira/browse/STORM-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293330#comment-15293330 ] ASF GitHub Bot commented on STORM-1475: --- Github user dossett commented on the pull request:

[GitHub] storm pull request: STORM-1475: Add storm-elasticsearch2 module

Github user dossett commented on the pull request: https://github.com/apache/storm/pull/1337#issuecomment-220600968 @HeartSaVioR You commented on ES 2.X in another PR (#1396). This PR adds an ES2.X bolt but essentially duplicates the code in the regular ES bolt (with very minor

[GitHub] storm pull request: Reorder to satisfy types lookup

Github user et1975 commented on the pull request: https://github.com/apache/storm/pull/1434#issuecomment-220597365 #1423 works, closing. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] storm pull request: Reorder to satisfy types lookup

Github user et1975 closed the pull request at: https://github.com/apache/storm/pull/1434 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] storm pull request: add hadoop-common dependency in README for sto...

GitHub user mazhechao opened a pull request: https://github.com/apache/storm/pull/1436 add hadoop-common dependency in README for storm-hdfs If hadoop-common is not included in pom.xml since storm-hdfs 1.0.0, we will get runtime errors. README should mention that. `

[GitHub] storm pull request: STORM-1475: Add storm-elasticsearch2 module

Github user mazhechao commented on the pull request: https://github.com/apache/storm/pull/1337#issuecomment-220527171 Yes, ES 2.x has released for a long peroid of time. It's a good news for us if storm support ES 2.x. --- If your project is set up for it, you can reply to this

[jira] [Commented] (STORM-1475) storm-elasticsearch should support ES 2.X

[ https://issues.apache.org/jira/browse/STORM-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292799#comment-15292799 ] ASF GitHub Bot commented on STORM-1475: --- Github user mazhechao commented on the pull request: