[jira] [Commented] (FLINK-4096) Nested FileOutputStream is not closed in JarFileCreator

[ https://issues.apache.org/jira/browse/FLINK-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369443#comment-15369443 ] ASF GitHub Bot commented on FLINK-4096: --- Github user zentol commented on the issue:

[GitHub] flink issue #2172: [FLINK-4096] Ensure JarOutputStream is always closed

Github user zentol commented on the issue: https://github.com/apache/flink/pull/2172 no, you are correct. --- 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, o

[GitHub] flink pull request #2224: {hotfix} fix errors and formatting in NiFi documen...

GitHub user smarthi opened a pull request: https://github.com/apache/flink/pull/2224 {hotfix} fix errors and formatting in NiFi documentation Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration. If y

[jira] [Commented] (FLINK-4053) Return value from Connection should be checked against null

[ https://issues.apache.org/jira/browse/FLINK-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369327#comment-15369327 ] ASF GitHub Bot commented on FLINK-4053: --- Github user mushketyk commented on the issu

[GitHub] flink issue #2128: [FLINK-4053] Return value from Connection should be check...

Github user mushketyk commented on the issue: https://github.com/apache/flink/pull/2128 Hi all. If this is fine and useful, could someone please merge this? --- 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

[jira] [Commented] (FLINK-4096) Nested FileOutputStream is not closed in JarFileCreator

[ https://issues.apache.org/jira/browse/FLINK-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369325#comment-15369325 ] ASF GitHub Bot commented on FLINK-4096: --- Github user mushketyk commented on the issu

[GitHub] flink issue #2172: [FLINK-4096] Ensure JarOutputStream is always closed

Github user mushketyk commented on the issue: https://github.com/apache/flink/pull/2172 Since jos is now used in try-with-resource, I assume it will be called in any case: https://github.com/apache/flink/pull/2172/files#diff-966966a476efb23e920314f9bf266539R192 Am I missi

[GitHub] flink issue #2169: [FLINK-3943] Add support for EXCEPT operator

Github user mushketyk commented on the issue: https://github.com/apache/flink/pull/2169 @twalthr Thank you for your review! I've update the PR according to your comments. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. I

[jira] [Commented] (FLINK-3943) Add support for EXCEPT (set minus)

[ https://issues.apache.org/jira/browse/FLINK-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369299#comment-15369299 ] ASF GitHub Bot commented on FLINK-3943: --- Github user mushketyk commented on the issu

[jira] [Commented] (FLINK-3190) Retry rate limits for DataStream API

[ https://issues.apache.org/jira/browse/FLINK-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369059#comment-15369059 ] ASF GitHub Bot commented on FLINK-3190: --- Github user fijolekProjects commented on th

[GitHub] flink issue #1954: [FLINK-3190] failure rate restart strategy

Github user fijolekProjects commented on the issue: https://github.com/apache/flink/pull/1954 Thanks for your patience @tillrohrmann :) I've replaced `FixedSizeFifoQueue` with `ArrayDeque` --- If your project is set up for it, you can reply to this email and have your reply appea

[GitHub] flink pull request #2214: [FLINK-4019][kinesis-connector] Use Kinesis record...

Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/2214 --- 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 enab

[jira] [Commented] (FLINK-4019) Expose approximateArrivalTimestamp through the KinesisDeserializationSchema interface

[ https://issues.apache.org/jira/browse/FLINK-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369031#comment-15369031 ] ASF GitHub Bot commented on FLINK-4019: --- Github user asfgit closed the pull request

[jira] [Resolved] (FLINK-4019) Expose approximateArrivalTimestamp through the KinesisDeserializationSchema interface

[ https://issues.apache.org/jira/browse/FLINK-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger resolved FLINK-4019. --- Resolution: Fixed Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/68277a43 >

[jira] [Updated] (FLINK-3516) JobManagerHACheckpointRecoveryITCase testCheckpointedStreamingSumProgram fails

[ https://issues.apache.org/jira/browse/FLINK-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-3516: -- Labels: test-stability (was: ) > JobManagerHACheckpointRecoveryITCase testCheckpointedStreaming

[jira] [Updated] (FLINK-3516) JobManagerHACheckpointRecoveryITCase testCheckpointedStreamingSumProgram fails

[ https://issues.apache.org/jira/browse/FLINK-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-3516: -- Component/s: JobManager Distributed Coordination > JobManagerHACheckpointRecove

[jira] [Commented] (FLINK-3516) JobManagerHACheckpointRecoveryITCase testCheckpointedStreamingSumProgram fails

[ https://issues.apache.org/jira/browse/FLINK-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369025#comment-15369025 ] Robert Metzger commented on FLINK-3516: --- Once again https://s3.amazonaws.com/archive

[jira] [Commented] (FLINK-4019) Expose approximateArrivalTimestamp through the KinesisDeserializationSchema interface

[ https://issues.apache.org/jira/browse/FLINK-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369001#comment-15369001 ] ASF GitHub Bot commented on FLINK-4019: --- Github user tzulitai commented on a diff in

[GitHub] flink pull request #2214: [FLINK-4019][kinesis-connector] Use Kinesis record...

Github user tzulitai commented on a diff in the pull request: https://github.com/apache/flink/pull/2214#discussion_r70164370 --- Diff: docs/apis/streaming/connectors/kinesis.md --- @@ -146,6 +146,50 @@ Also note that Flink can only restart the topology if enough processing slots ar

[jira] [Commented] (FLINK-4019) Expose approximateArrivalTimestamp through the KinesisDeserializationSchema interface

[ https://issues.apache.org/jira/browse/FLINK-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368993#comment-15368993 ] ASF GitHub Bot commented on FLINK-4019: --- Github user rmetzger commented on a diff in

[GitHub] flink pull request #2214: [FLINK-4019][kinesis-connector] Use Kinesis record...

Github user rmetzger commented on a diff in the pull request: https://github.com/apache/flink/pull/2214#discussion_r70164121 --- Diff: docs/apis/streaming/connectors/kinesis.md --- @@ -146,6 +146,50 @@ Also note that Flink can only restart the topology if enough processing slots ar