[jira] [Commented] (BEAM-242) Enable Checkstyle check and Javadoc build for the Flink Runner

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

[GitHub] incubator-beam pull request: [BEAM-242] Fix javadoc on Flink runner.

Github user jbonofre closed the pull request at: https://github.com/apache/incubator-beam/pull/382 --- 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

[incubator-beam] Git Push Summary

Repository: incubator-beam Updated Tags: refs/tags/0.1.0-incubating-1 [created] a5a289b6c

incubator-beam git commit: [maven-release-plugin] rollback changes from release preparation of 0.1.0-incubating-1

Repository: incubator-beam Updated Branches: refs/heads/release-0.1.0-incubating 2a25d32f0 -> 962d8da06 [maven-release-plugin] rollback changes from release preparation of 0.1.0-incubating-1 Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit:

Jenkins build became unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #452

See

[2/2] incubator-beam git commit: This closes #403

This closes #403 Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/a829d9ca Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam/tree/a829d9ca Diff:

[1/2] incubator-beam git commit: [BEAM-242] Set javadoc less strict around missing return or param statements

Repository: incubator-beam Updated Branches: refs/heads/master b2f69504a -> a829d9caf [BEAM-242] Set javadoc less strict around missing return or param statements Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit:

[jira] [Commented] (BEAM-242) Enable Checkstyle check and Javadoc build for the Flink Runner

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

[jira] [Commented] (BEAM-318) AvroCoder is vulnerable to AVRO-607

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

[jira] [Created] (BEAM-318) AvroCoder is vulnerable to AVRO-607

Daniel Halperin created BEAM-318: Summary: AvroCoder is vulnerable to AVRO-607 Key: BEAM-318 URL: https://issues.apache.org/jira/browse/BEAM-318 Project: Beam Issue Type: Bug

[GitHub] incubator-beam pull request: Add KEYS file

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/405 --- 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

[1/2] incubator-beam git commit: Add KEYS file

Repository: incubator-beam Updated Branches: refs/heads/master 00ab9b5b5 -> b2f69504a Add KEYS file Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/65753190 Tree:

[2/2] incubator-beam git commit: This closes #405

This closes #405 Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/b2f69504 Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam/tree/b2f69504 Diff:

[GitHub] incubator-beam pull request: [BEAM-318] AvroCoder,Source: workaround AVRO-60...

GitHub user dhalperi opened a pull request: https://github.com/apache/incubator-beam/pull/408 [BEAM-318] AvroCoder,Source: workaround AVRO-607 See https://issues.apache.org/jira/browse/AVRO-607 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308890#comment-15308890 ] Pawel Szczur commented on BEAM-315: --- [~frances] Thanks for explanation. The bug appears with Beam' build

[jira] [Commented] (BEAM-122) GlobalWindow and allowedLateness can cause inconsistent timer interpretation

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

[GitHub] incubator-beam pull request: [BEAM-122] Forward port changes to backport

GitHub user mshields822 opened a pull request: https://github.com/apache/incubator-beam/pull/407 [BEAM-122] Forward port changes to backport R: @bjchambers You can merge this pull request into a Git repository by running: $ git pull

[GitHub] incubator-beam pull request: [BEAM-155] Use custom Assertions in Spark Strea...

GitHub user tgroh opened a pull request: https://github.com/apache/incubator-beam/pull/406 [BEAM-155] Use custom Assertions in Spark Streaming Tests Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR

[jira] [Commented] (BEAM-155) Support asserting the contents of windows and panes in PAssert

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

[GitHub] incubator-beam pull request: Add KEYS file

GitHub user jbonofre opened a pull request: https://github.com/apache/incubator-beam/pull/405 Add KEYS file Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [X] Make sure the PR title is formatted like: `[BEAM-]

[GitHub] incubator-beam pull request: Fix github template and exclude from rat check

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/404 --- 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

[GitHub] incubator-beam pull request: [BEAM-242] Set javadoc less strict around missi...

GitHub user jbonofre opened a pull request: https://github.com/apache/incubator-beam/pull/403 [BEAM-242] Set javadoc less strict around missing return or param sta… Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [X]

[jira] [Resolved] (BEAM-254) Add maven-rat-plugin execution

[ https://issues.apache.org/jira/browse/BEAM-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Bonaci resolved BEAM-254. --- Resolution: Fixed > Add maven-rat-plugin execution > -- > >

[jira] [Commented] (BEAM-254) Add maven-rat-plugin execution

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

[1/2] incubator-beam git commit: [BEAM-254] Add apache-rat-plugin execution and fix files with missing license header

Repository: incubator-beam Updated Branches: refs/heads/master 731c03036 -> 6c338da0d [BEAM-254] Add apache-rat-plugin execution and fix files with missing license header Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit:

[GitHub] incubator-beam pull request: [BEAM-254] Add apache-rat-plugin execution and ...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/297 --- 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

[2/2] incubator-beam git commit: This closes #297

This closes #297 Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/6c338da0 Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam/tree/6c338da0 Diff:

[jira] [Created] (BEAM-317) Implement PAssert#containsInAnyOrder and PAssert#satisfies without using Side Inputs

Thomas Groh created BEAM-317: Summary: Implement PAssert#containsInAnyOrder and PAssert#satisfies without using Side Inputs Key: BEAM-317 URL: https://issues.apache.org/jira/browse/BEAM-317 Project: Beam

[jira] [Commented] (BEAM-53) PubSubIO: reimplement in Java

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

[GitHub] incubator-beam pull request: [BEAM-53] PubSub: build fixups

Github user dhalperi closed the pull request at: https://github.com/apache/incubator-beam/pull/367 --- 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

[GitHub] incubator-beam pull request: AvroSource: synchronization fix

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/373 --- 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

[1/2] incubator-beam git commit: AvroSource: synchronization fix

Repository: incubator-beam Updated Branches: refs/heads/master 2ffecfda2 -> 731c03036 AvroSource: synchronization fix Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/20a58873 Tree:

[jira] [Commented] (BEAM-316) Support file scheme in TextIO

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

[GitHub] incubator-beam pull request: [BEAM-316] Add file scheme support in TextIO

GitHub user jbonofre opened a pull request: https://github.com/apache/incubator-beam/pull/402 [BEAM-316] Add file scheme support in TextIO Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [X] Make sure the PR title is

[jira] [Created] (BEAM-316) Support file scheme in TextIO

Jean-Baptiste Onofré created BEAM-316: - Summary: Support file scheme in TextIO Key: BEAM-316 URL: https://issues.apache.org/jira/browse/BEAM-316 Project: Beam Issue Type: Improvement

[jira] [Comment Edited] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307958#comment-15307958 ] Pawel Szczur edited comment on BEAM-315 at 5/31/16 3:50 PM: I've tried to set

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307958#comment-15307958 ] Pawel Szczur commented on BEAM-315: --- I've tried to set {options.setStreaming(true)} it seams that items

[jira] [Issue Comment Deleted] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawel Szczur updated BEAM-315: -- Comment: was deleted (was: I've tried {{options.setStreaming(true)}} it caused:

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307925#comment-15307925 ] Pawel Szczur commented on BEAM-315: --- I've tried {{options.setStreaming(true)}} it caused:

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307853#comment-15307853 ] Maximilian Michels commented on BEAM-315: - It appears this is only a problem in the batch execution

[jira] [Updated] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated BEAM-315: Summary: GroupByKey/CoGroupByKey doesn't group correctly in batch mode of FlinkPipelineRunner

[jira] [Comment Edited] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307833#comment-15307833 ] Pawel Szczur edited comment on BEAM-315 at 5/31/16 2:51 PM: Using bleeding-edge

[jira] [Comment Edited] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307833#comment-15307833 ] Pawel Szczur edited comment on BEAM-315 at 5/31/16 2:50 PM: Using bleeding-edge

[jira] [Comment Edited] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307833#comment-15307833 ] Pawel Szczur edited comment on BEAM-315 at 5/31/16 2:51 PM: Using bleeding-edge

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307833#comment-15307833 ] Pawel Szczur commented on BEAM-315: --- Using bleeding-edge of Beam. The bug appears with different key

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307827#comment-15307827 ] Aljoscha Krettek commented on BEAM-315: --- I attached a version that uses a {{String}} as key. With

[jira] [Updated] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aljoscha Krettek updated BEAM-315: -- Attachment: CoGroupPipelineStringKey.java This is a version of the same program that uses a

[jira] [Commented] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307796#comment-15307796 ] Maximilian Michels commented on BEAM-315: - Thanks for reporting! I'm assuming you're using the

[jira] [Commented] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

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

[GitHub] incubator-beam pull request: [BEAM-313] Enable the use of an existing spark ...

GitHub user amarouni opened a pull request: https://github.com/apache/incubator-beam/pull/401 [BEAM-313] Enable the use of an existing spark context with the SparkPipelineRunner The general use case is that the SparkPipelineRunner creates its own Spark context and uses it for the

[jira] [Updated] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawel Szczur updated BEAM-315: -- Description: Same keys are processed multiple times. A repo to reproduce the bug:

[jira] [Updated] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawel Szczur updated BEAM-315: -- Description: Same keys is processed multiple times. A repo to reproduce the bug:

[jira] [Created] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner

Pawel Szczur created BEAM-315: - Summary: GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner Key: BEAM-315 URL: https://issues.apache.org/jira/browse/BEAM-315 Project: Beam

[jira] [Commented] (BEAM-314) Support zip compression in TextIO

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

[jira] [Commented] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307605#comment-15307605 ] Jean-Baptiste Onofré commented on BEAM-313: --- Right now, each runner provides its own context, and

[jira] [Assigned] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned BEAM-313: - Assignee: Jean-Baptiste Onofré > Enable the use of an existing spark context with

[jira] [Commented] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ https://issues.apache.org/jira/browse/BEAM-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307533#comment-15307533 ] Ismaël Mejía commented on BEAM-313: --- [~amitsela] What do you think about this ? The use case is not pure

[jira] [Created] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

Abbass Marouni created BEAM-313: --- Summary: Enable the use of an existing spark context with the SparkPipelineRunner Key: BEAM-313 URL: https://issues.apache.org/jira/browse/BEAM-313 Project: Beam

[2/2] incubator-beam git commit: This closes #398

This closes #398 Project: http://git-wip-us.apache.org/repos/asf/incubator-beam/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam/commit/2ffecfda Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam/tree/2ffecfda Diff:

[GitHub] incubator-beam pull request: [BEAM-270] remove CoGroupByKey transl...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-beam/pull/398 --- 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

[jira] [Commented] (BEAM-270) Support Timestamps/Windows in Flink Batch

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