[GitHub] storm pull request #1985: STORM-2371: New eventhub implementation

[SreeramGarlapati]

Github user SreeramGarlapati commented on a diff in the pull request:

https://github.com/apache/storm/pull/1985#discussion_r104280323
  
--- Diff: 
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/spout/EventDataScheme.java
 ---
@@ -46,25 +42,11 @@
private static final long serialVersionUID = 1L;
 
@Override
-   public List deserialize(Message message) {
+   public List deserialize(EventData eventData) {
final List fieldContents = new ArrayList();
-
-   Map metaDataMap = new HashMap();
String messageData = "";
-
-   for (Section section : message.getPayload()) {
-   if (section instanceof Data) {
-   Data data = (Data) section;
-   messageData = new 
String(data.getValue().getArray());
-   } else if (section instanceof AmqpValue) {
-   AmqpValue amqpValue = (AmqpValue) section;
-   messageData = amqpValue.getValue().toString();
-   } else if (section instanceof ApplicationProperties) {
-   final ApplicationProperties 
applicationProperties = (ApplicationProperties) section;
-   metaDataMap = applicationProperties.getValue();
-   }
-   }
-
+   messageData = new String 
(eventData.getBody(),eventData.getBodyOffset(),eventData.getBodyLength(),Charset.defaultCharset());
--- End diff --

Null check getBody


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1985: STORM-2371: New eventhub implementation

[SreeramGarlapati]

Github user SreeramGarlapati commented on a diff in the pull request:

https://github.com/apache/storm/pull/1985#discussion_r104280244
  
--- Diff: 
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/spout/StringEventDataScheme.java
 ---
@@ -46,19 +39,11 @@
   private static final long serialVersionUID = 1L;
 
   @Override
-  public List deserialize(Message message) {
+  public List deserialize(EventData eventData) {
 final List fieldContents = new ArrayList();
-
-for (Section section : message.getPayload()) {
-  if (section instanceof Data) {
-Data data = (Data) section;
-fieldContents.add(new String(data.getValue().getArray()));
-  } else if (section instanceof AmqpValue) {
-AmqpValue amqpValue = (AmqpValue) section;
-fieldContents.add(amqpValue.getValue().toString());
-  }
-}
-
+String messageData = "";
+messageData = new String 
(eventData.getBody(),eventData.getBodyOffset(),eventData.getBodyLength(),Charset.defaultCharset());
--- End diff --

Add null check for getbody()


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1985: STORM-2371: New eventhub implementation

[SreeramGarlapati]

Github user SreeramGarlapati commented on a diff in the pull request:

https://github.com/apache/storm/pull/1985#discussion_r104280523
  
--- Diff: 
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/spout/EventHubReceiverImpl.java
 ---
@@ -65,77 +60,80 @@ public EventHubReceiverImpl(EventHubSpoutConfig config, 
String partitionId) {
   }
 
   @Override
-  public void open(IEventHubFilter filter) throws EventHubException {
-logger.info("creating eventhub receiver: partitionId=" + partitionId + 
-   ", filterString=" + filter.getFilterString());
+  public void open(String offset) throws EventHubException {
+logger.info("creating eventhub receiver: partitionId=" + partitionId +
+", offset=" + offset);
 long start = System.currentTimeMillis();
-receiver = new ResilientEventHubReceiver(connectionString, entityName,
-   partitionId, consumerGroupName, defaultCredits, filter);
-receiver.initialize();
-
+try {
+  ehClient = 
EventHubClient.createFromConnectionStringSync(connectionString);
+  receiver = ehClient.createEpochReceiverSync(
+  consumerGroupName,
+  partitionId,
+  offset,
+  false,
+  1);
--- End diff --

Please refrain from using catch all exceptions and move to catching more 
specific exceptions...


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1981: STORM 2391 - Move HdfsSpoutTopology from storm-sta...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/storm/pull/1981


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1983: (1.x) STORM-2389 Avoid instantiating Event Logger ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/storm/pull/1983


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1982: STORM-2389 Avoid instantiating Event Logger when t...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/storm/pull/1982


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1960: STORM-1772 Adding Perf module with topologies for measuri...

[roshannaik]

Github user roshannaik commented on the issue:

https://github.com/apache/storm/pull/1960
  
@harshach   FYI: I have squashed the commits. Also addressed rat issues.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [CANCELED] [VOTE] Release Apache Storm 1.1.0 (RC2)

[Roshan Naik]

As having a separate module for each of the connectors will cause a lot of 
bloat … may be good to club them into one.

-roshan


On 3/2/17, 10:39 AM, "Sree V"  wrote:

+1separate main binaries, connectors and samples/examples.
 
Thanking you.
With Regards
Sree 

On Thursday, March 2, 2017 8:02 AM, Satish Duggana 
 wrote:
 

 Agree that such huge binaries may not be acceptable. We should really think
about the options proposed earlier like excluding some of the external
connectors from binary and update the documentation respectively.

Thanks,
Satish.

On Thu, Mar 2, 2017 at 4:41 PM, Jungtaek Lim  wrote:

> Adding my observation to my last mail:
> I just give STORM-2249 a try (against master branch) and compare before vs
> after.
> It adds more than 300 MB, and the final archive is more than 550 MB. I
> guess it would be similar for 1.x branch.
>
> Before --
> -rw-r--r--  1 jlim  staff  3.3K  3  2 19:41 apache-storm-2.0.0-SNAPSHOT.
> pom
> -rw-r--r--  1 jlim  staff  473B  3  2 19:41 apache-storm-2.0.0-SNAPSHOT.
> pom.asc
> -rw-r--r--  1 jlim  staff  264M  3  2 19:41 apache-storm-2.0.0-SNAPSHOT.
> tar.gz
> -rw-r--r--  1 jlim  staff  473B  3  2 19:41 apache-storm-2.0.0-SNAPSHOT.
> tar.gz.asc
> -rw-r--r--  1 jlim  staff  264M  3  2 19:41 apache-storm-2.0.0-SNAPSHOT.
> zip
> -rw-r--r--  1 jlim  staff  473B  3  2 19:41 apache-storm-2.0.0-SNAPSHOT.
> zip.asc
>
> After ---
> -rw-r--r--  1 jlim  staff  3.3K  3  2 19:46 apache-storm-2.0.0-SNAPSHOT.
> pom
> -rw-r--r--  1 jlim  staff  473B  3  2 19:46 apache-storm-2.0.0-SNAPSHOT.
> pom.asc
> -rw-r--r--  1 jlim  staff  564M  3  2 19:46 apache-storm-2.0.0-SNAPSHOT.
> tar.gz
> -rw-r--r--  1 jlim  staff  473B  3  2 19:46 apache-storm-2.0.0-SNAPSHOT.
> tar.gz.asc
> -rw-r--r--  1 jlim  staff  565M  3  2 19:46 apache-storm-2.0.0-SNAPSHOT.
> zip
> -rw-r--r--  1 jlim  staff  473B  3  2 19:47 apache-storm-2.0.0-SNAPSHOT.
> zip.asc
>
> While 264M is already a bit huge for me, 564M is not that I can accept.
> (Binary dist. of Flink 1.2.0 is 127M, Spark 2.1.0 is 195M, Kafka 0.10.2 is
> 37M.)
>
> Btw, we're including source code of examples, and "mvn clean package" will
> work for every example modules.
>
> 2017년 3월 2일 (목) 오전 11:29, Jungtaek Lim 님이 작성:
>
> > I guess it might be good time to think why we add all connectors to the
> > binary distribution.
> >
> > Spark and Flink don't include them to binary dist. They even moved some
> or
> > most of connectors out of repo, have been maintaining them in Apache
> Bahir.
> > (Personally this is something I'm in favor of. We have lots of 
connectors
> > and many of them are outdated - clear example is storm-elasticsearch.)
> >
> > If we are assuming online then we don't even need to think about users
> > touching binary dist. version of connectors. Users have been including
> them
> > via build tools' dependency management, or even starting 1.1.0, users 
can
> > include them via '--artifact' option.
> >
> > I also was just one of users for Storm, and I haven't use them directly.
> > How much UX gets worse when we remove connectors to binary dist? It only
> > helps some users who are not connected to the internet, and IMHO it's a
> > rare case.
> >
> > I would like to see the opposite approach, removing all connectors (or
> > just keeping storm-kafka/storm-kafka-client and some more preferred
> things)
> > and its relevant examples from binary dist.
> >
> > What do you think about it?
> >
> > - Jungtaek Lim (HeartSaVioR)
> >
> >
> > 2017년 3월 2일 (목) 오전 10:23, Roshan Naik 님이 작성:
> >
> > Once all of the shaded examples are included the size will go up 
further.
> >
> > But currently as they are not part of the tar.gz … something else is the
> > culprit for the bloat.
> >
> >
> >
> > Below is a comparative listing of 1.0.3 vs 1.1.0  binary releases .. of
> > files that are larger than 4MB.
> >
> >
> >
> >
> >
> > @Jungtaek Lim :  I am thinking, since the
> > code for the examples can be easily viewed online … it would be valuable
> to
> > have the executable topologies made available to the user as part of the
> > binary release … rather have them figure out how to build it correctly
> > before trying them out.
> >
> >
> >
> > -roshan
> >
> >
> >
> >
> >
> > ➜  apache-storm-1.0.3 >  find . -type f -size +4096 -exec ls -lh {} \;
> >
> > -rw-r--r--@ 1 roshan  staff70M Feb  7 

Ideas for storing state in Spout

[S G]

Hi,

We are writing a spout that needs to store its progress and unlike kafka,
the datastore here has no concept of storing offsets.

I looked at IStatefulBolt but that seems to be usable only for Bolts.
Any idea if an IStatefulSpout is planned for the recent future?
Thinking aloud, IStatefulSpout seems like would be a much more common
requirement than IStatefulBolt because its usually the spouts that keep
track of their progress while the bolts are just stateless (most of the
time) and idempotent (most of the time).

Also, is there a guide to use zookeeper for such use-cases?
I see some classes like org.apache.storm.zookeeper.Zookeeper and
org.apache.storm.utils.Utils which have some zookeeper related methods.

Is it a good idea to use these classes for storing some offsets in
zookeeper (data is not too heavy size wise and frequency of storage is
configurable) or wait for IStatefulSpout (if any is planned) ?


Thanks
SG

[GitHub] storm pull request #1988: STORM-2395: storm.cmd supervisor calls the wrong c...

[alexlehm]

GitHub user alexlehm opened a pull request:

https://github.com/apache/storm/pull/1988

STORM-2395: storm.cmd supervisor calls the wrong class name

use org.apache.storm.daemon.supervisor.Supervisor instead

Signed-off-by: alexlehm 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alexlehm/storm 
STORM-2395-storm-supervisor-windows

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/storm/pull/1988.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1988


commit 49573935dfccd74de43f55f4829263695e1d35e8
Author: alexlehm 
Date:   2017-03-03T23:10:52Z

STORM-2395: storm.cmd supervisor calls the wrong class name
use org.apache.storm.daemon.supervisor.Supervisor instead

Signed-off-by: alexlehm 




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1975: STORM-2386 Fail-back Blob deletion also fails in B...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/storm/pull/1975


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1976: STORM-2386 Fail-back Blob deletion also fails in B...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/storm/pull/1976


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1985: STORM-2371: New eventhub implementation

[rban1]

Github user rban1 commented on a diff in the pull request:

https://github.com/apache/storm/pull/1985#discussion_r104231241
  
--- Diff: 
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/spout/EventHubReceiverImpl.java
 ---
@@ -65,77 +60,80 @@ public EventHubReceiverImpl(EventHubSpoutConfig config, 
String partitionId) {
   }
 
   @Override
-  public void open(IEventHubFilter filter) throws EventHubException {
-logger.info("creating eventhub receiver: partitionId=" + partitionId + 
-   ", filterString=" + filter.getFilterString());
+  public void open(String offset) throws EventHubException {
+logger.info("creating eventhub receiver: partitionId=" + partitionId +
+", offset=" + offset);
 long start = System.currentTimeMillis();
-receiver = new ResilientEventHubReceiver(connectionString, entityName,
-   partitionId, consumerGroupName, defaultCredits, filter);
-receiver.initialize();
-
+try {
+  ehClient = 
EventHubClient.createFromConnectionStringSync(connectionString);
+  receiver = ehClient.createEpochReceiverSync(
+  consumerGroupName,
+  partitionId,
+  offset,
+  false,
+  1);
+}catch (Exception e){
+  logger.info("Exception in creating EventhubClient"+e.toString());
+}
 long end = System.currentTimeMillis();
 logger.info("created eventhub receiver, time taken(ms): " + 
(end-start));
   }
 
   @Override
-  public void close() {
+  public void close(){
 if(receiver != null) {
-  receiver.close();
+  try {
+receiver.close().whenComplete((voidargs,error)->{
+  try{
+if(error!=null){
+  logger.error("Exception during receiver close 
phase"+error.toString());
+}
+ehClient.closeSync();
+  }catch (Exception e){
+logger.error("Exception during ehclient close 
phase"+e.toString());
+  }
+}).get();
+  }catch (InterruptedException e){
+logger.error("Exception occured during close phase"+e.toString());
+  }catch (ExecutionException e){
+logger.error("Exception occured during close phase"+e.toString());
+  }
   logger.info("closed eventhub receiver: partitionId=" + partitionId );
   receiver = null;
+  ehClient =  null;
 }
   }
+
   
   @Override
   public boolean isOpen() {
 return (receiver != null);
   }
 
   @Override
-  public EventData receive(long timeoutInMilliseconds) {
+  public EventDataWrap receive() {
 long start = System.currentTimeMillis();
-Message message = receiver.receive(timeoutInMilliseconds);
+Iterable receivedEvents=null;
+/*Get one message at a time for backward compatibility behaviour*/
+try {
+  receivedEvents = receiver.receiveSync(1);
+}catch (Exception e){
+  logger.error("Exception occured during receive"+e.toString());
+}
 long end = System.currentTimeMillis();
 long millis = (end - start);
 receiveApiLatencyMean.update(millis);
 receiveApiCallCount.incr();
-
-if (message == null) {
-  //Temporary workaround for AMQP/EH bug of failing to receive messages
-  /*if(timeoutInMilliseconds > 100 && millis < 
timeoutInMilliseconds/2) {
-throw new RuntimeException(
-"Restart EventHubSpout due to failure of receiving messages in 
"
-+ millis + " millisecond");
-  }*/
+if (receivedEvents == null) {
--- End diff --

check for length also


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1982: STORM-2389 Avoid instantiating Event Logger when topology...

[harshach]

Github user harshach commented on the issue:

https://github.com/apache/storm/pull/1982
  
+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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1983: (1.x) STORM-2389 Avoid instantiating Event Logger when to...

[harshach]

Github user harshach commented on the issue:

https://github.com/apache/storm/pull/1983
  
+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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1985: STORM-2371: New eventhub implementation

[rban1]

Github user rban1 commented on a diff in the pull request:

https://github.com/apache/storm/pull/1985#discussion_r104228014
  
--- Diff: 
external/storm-eventhubs/src/main/java/org/apache/storm/eventhubs/bolt/EventHubBolt.java
 ---
@@ -18,14 +18,16 @@
 package org.apache.storm.eventhubs.bolt;
 
 import java.util.Map;
+import java.util.concurrent.ExecutionException;
--- End diff --

order the imports


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1985: STORM-2371: New eventhub implementation

[rban1]

Github user rban1 commented on a diff in the pull request:

https://github.com/apache/storm/pull/1985#discussion_r104227737
  
--- Diff: external/storm-eventhubs/pom.xml ---
@@ -95,6 +95,11 @@
 ${eventhubs.client.version}
 
 
+com.microsoft.azure
+azure-eventhubs
+0.11.0
--- End diff --

make it a property


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1985: STORM-2371: New eventhub implementation

[srdo]

Github user srdo commented on the issue:

https://github.com/apache/storm/pull/1985
  
I think you should push these changes back to your previous PR here 
https://github.com/apache/storm/pull/1951, otherwise it's hard to know which 
comments you're talking about. It also makes it harder for reviewers to know 
whether an issue has already been discussed.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1987: 1 x branch

[qiuwsh]

Github user qiuwsh closed the pull request at:

https://github.com/apache/storm/pull/1987


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1987: 1 x branch

[qiuwsh]

GitHub user qiuwsh opened a pull request:

https://github.com/apache/storm/pull/1987

1 x branch



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/storm 1.x-branch

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/storm/pull/1987.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1987


commit 6ed99200c985e1b4e8ac2124a854e83d8921c2e3
Author: itiel 
Date:   2016-12-03T16:45:04Z

fix actiavte and deactive heartbeat problem

commit 4f2be9d3127643a4a5b1b067171e854ea03e8695
Author: Jungtaek Lim 
Date:   2016-12-06T23:14:08Z

Merge branch 'STORM-2234-1.x-merge' into 1.x-branch

commit ffb05137815c6bcbaff7d5c879bcd6abba79ad73
Author: Jungtaek Lim 
Date:   2016-12-06T23:15:12Z

add STORM-2234 to CHANGELOG

commit c64a109529f00e6c9e969b99d8d03a64d2f32069
Author: Kyle Nusbaum 
Date:   2016-12-02T19:46:21Z

Updating Trident RAS Documentation.

commit cce525b2df1b2c6a93423700434c52b6a03e66bb
Author: Jungtaek Lim 
Date:   2016-12-06T23:36:57Z

Merge branch 'PR-1812-1.x-merge' into 1.x-branch

commit 3b378e4fd8ce359856f294c344f5ddc0ff652c73
Author: Jungtaek Lim 
Date:   2016-12-06T06:36:23Z

STORM-2235 Introduce new option: 'add remote repositories' for dependency 
resolver

* add '--artifactRepositories' option to pull the artifacts from other than 
Maven Central

commit be4efc3e17c25f0dcb609483d29e0b600282d415
Author: Jungtaek Lim 
Date:   2016-12-08T11:13:38Z

Merge branch 'STORM-2235-1.x' into 1.x-branch

commit 0cd627f7c5294f42f40b1e313194275b38312f25
Author: Jungtaek Lim 
Date:   2016-12-08T11:14:05Z

STORM-2235: CHANGELOG

commit 1bfff31da87d6913a4cfff95a9c6f14f6f001dd7
Author: marblejenka 
Date:   2016-12-11T09:48:51Z

modified incorrect and broken links

commit c149fe1e169e682c43981ffa02550afead5e
Author: vesense 
Date:   2016-12-13T03:09:30Z

Merge branch '1.x-branch-fixed-Structure-of-the-codebase' of 
https://github.com/marblejenka/storm into 1.x-branch

commit 5c17a59ebf9f5667ccfb2dc0a127044b94a0de86
Author: Jeff Fenchel 
Date:   2016-09-11T01:32:35Z

STORM-2087: storm-kafka-client improvements for kafka 0.10
 - Added unit tests to storm-kafka-client
 - Fixed bug in kafka-spout-client that resulted in tuples not being  
replayed
when a failure occurred immediately after the last commit
 - Modified the kafka spout to continue processing and not halt upon 
receiving
a double ack

commit e47ccecba855889b75da40a3cceb190587552aef
Author: Stig Rohde Døssing 
Date:   2016-12-14T18:29:48Z

STORM-2087: Make tests Java 7 compatible

commit 9ecf82c56e0d1882d1a30442fdd6d59e189b4a36
Author: Hugo Louro 
Date:   2016-12-17T08:57:13Z

Fix typo in flux.md

commit 7802298f1993af9dbce9e6b8b23c4d4ffd933ba0
Author: Arun Mahadevan 
Date:   2016-12-13T10:53:35Z

STORM-2246: Logviewer download link has urlencoding on part of the URL

Changed the URL format for "Download full file" link under worker logs
from "download/URLENCODED()" to 
"download?file=URLENCODED()"

commit c65223a7192409557c179b4eced7dd3dd250f6a7
Author: Jungtaek Lim 
Date:   2016-12-18T11:41:37Z

Merge branch 'STORM-2246-1.x-merge' into 1.x-branch

commit 3c6abc8f75b74d7ce464bdfc32530d4ffaa8c8b4
Author: Jungtaek Lim 
Date:   2016-12-18T11:42:02Z

STORM-2246: CHANGELOG

commit 032592a892356e36fd3848b1f1692099eed90d28
Author: Arun Mahadevan 
Date:   2016-12-08T15:48:12Z

[STORM-2238] Add Timestamp extractor for windowed bolt

Added a timestamp extractor so that the tuple timestamp can be derived from 
the tuple than directly
mapping it to a field within the tuple.

commit 7bf95d6644b294bd456e08386fe59ed1c78e0c5e
Author: Jungtaek Lim 
Date:   2016-12-18T22:28:13Z

Merge branch 'STORM-2238-1.x' of https://github.com/arunmahadevan/storm 
into STORM-2238-1.x-merge

commit 7701bf4ea99aa1a5ee34984c489f4de1eb495a73
Author: Jungtaek Lim 
Date:   2016-12-18T22:28:32Z

STORM-2238: CHANGELOG

commit 8310f593c239577e65c2e955385320b95ed825f7
Author: Jungtaek Lim 
Date:   2016-12-20T07:42:54Z

Merge branch 'STORM-2087-1.x' of https://github.com/srdo/storm into 
STORM-2087-1.x-merge

commit 55b3099e1fdc297f235f57560d21ed160632835e
Author: Jungtaek Lim 
Date:   2016-12-20T07:45:15Z

STORM-2087: CHANGELOG

commit 145af644324b62f2c060c6e795ac6b5474fd17d2
Author: Stig Rohde Døssing