[GitHub] flink pull request #3738: [FLINK-6311] [Kinesis Connector] NPE in FlinkKines...

2017-04-20 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/flink/pull/3738


---
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] flink pull request #3738: [FLINK-6311] [Kinesis Connector] NPE in FlinkKines...

2017-04-19 Thread tzulitai
Github user tzulitai commented on a diff in the pull request:

https://github.com/apache/flink/pull/3738#discussion_r112302446
  
--- Diff: 
flink-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/internals/KinesisDataFetcher.java
 ---
@@ -408,12 +408,15 @@ public void runFetcher() throws Exception {
 */
public void shutdownFetcher() {
running = false;
-   mainThread.interrupt(); // the main thread may be sleeping for 
the discovery interval
-
+   if (mainThread != null) {
+   mainThread.interrupt(); // the main thread may be 
sleeping for the discovery interval
+   }
if (LOG.isInfoEnabled()) {
LOG.info("Shutting down the shard consumer threads of 
subtask {} ...", indexOfThisConsumerSubtask);
}
-   shardConsumersExecutor.shutdownNow();
+   if (shardConsumersExecutor != null) {
--- End diff --

Actually I think this is a redundant `null` check, because 
`shardConsumersExecutor` is final.
It should never be null, so this null check might actually be confusing to 
other readers.


---
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] flink pull request #3738: [FLINK-6311] [Kinesis Connector] NPE in FlinkKines...

2017-04-19 Thread zhangminglei
GitHub user zhangminglei opened a pull request:

https://github.com/apache/flink/pull/3738

[FLINK-6311] [Kinesis Connector] NPE in FlinkKinesisConsumer if sourc…

…e was closed before run.

Thanks for contributing to Apache Flink. Before you open your pull request, 
please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your 
pull request. For more information and/or questions please refer to the [How To 
Contribute guide](http://flink.apache.org/how-to-contribute.html).
In addition to going through the list, please provide a meaningful 
description of your changes.

- [ ] General
  - The pull request references the related JIRA issue ("[FLINK-XXX] Jira 
title text")
  - The pull request addresses only one issue
  - Each commit in the PR has a meaningful commit message (including the 
JIRA id)

- [ ] Documentation
  - Documentation has been added for new functionality
  - Old documentation affected by the pull request has been updated
  - JavaDoc for public methods has been added

- [ ] Tests & Build
  - Functionality added by the pull request is covered by tests
  - `mvn clean verify` has been executed successfully locally or a Travis 
build has passed


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

$ git pull https://github.com/zhangminglei/flink flink-6311

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

https://github.com/apache/flink/pull/3738.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 #3738


commit ff6dcea5fc3a1f8ebb8aca73d61736818b9fa7f3
Author: zhangminglei 
Date:   2017-04-19T09:43:57Z

[FLINK-6311] [Kinesis Connector] NPE in FlinkKinesisConsumer if source was 
closed before run.




---
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.
---