[jira] [Updated] (BEAM-2636) user_score on DataflowRunner is broken

[ https://issues.apache.org/jira/browse/BEAM-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated BEAM-2636: --- Fix Version/s: 2.1.0 > user_score on DataflowRunner is broken > ---

[jira] [Commented] (BEAM-2575) ApexRunner doesn't emit watermarks for additional outputs

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

[jira] [Commented] (BEAM-2636) user_score on DataflowRunner is broken

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

[2/2] beam git commit: This closes #3627

This closes #3627 Project: http://git-wip-us.apache.org/repos/asf/beam/repo Commit: http://git-wip-us.apache.org/repos/asf/beam/commit/04899e41 Tree: http://git-wip-us.apache.org/repos/asf/beam/tree/04899e41 Diff: http://git-wip-us.apache.org/repos/asf/beam/diff/04899e41 Branch: refs/heads/relea

[1/2] beam git commit: [BEAM-2636] Make sure we only override the correct class

Repository: beam Updated Branches: refs/heads/release-2.1.0 c7c777d8b -> 04899e414 [BEAM-2636] Make sure we only override the correct class Project: http://git-wip-us.apache.org/repos/asf/beam/repo Commit: http://git-wip-us.apache.org/repos/asf/beam/commit/ab21078b Tree: http://git-wip-us.apa

[GitHub] beam pull request #3627: [BEAM-2636] Make sure we only override the correct ...

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

Jenkins build is still unstable: beam_PostCommit_Java_MavenInstall #4449

See

Jenkins build is still unstable: beam_PostCommit_Java_MavenInstall #4443

See

[3/4] beam git commit: [BEAM-2571] Change DoFnOperator to use Long.MAX_VALUE as max watermark

[BEAM-2571] Change DoFnOperator to use Long.MAX_VALUE as max watermark This is in line with what Flink does and what BoundedSourceWrapper and UnboundedSourceWrapper do. Project: http://git-wip-us.apache.org/repos/asf/beam/repo Commit: http://git-wip-us.apache.org/repos/asf/beam/commit/84499317 T

[1/4] beam git commit: [BEAM-2571] Respect watermark contract in Flink DoFnOperator

Repository: beam Updated Branches: refs/heads/master 5f1d1365b -> f54072a1b [BEAM-2571] Respect watermark contract in Flink DoFnOperator In Flink, a watermark T specifies that there will be no elements with a timestamp <= T in the future. In Beam, a watermark T specifies that there will not be

[4/4] beam git commit: This closes #3600

This closes #3600 Project: http://git-wip-us.apache.org/repos/asf/beam/repo Commit: http://git-wip-us.apache.org/repos/asf/beam/commit/f54072a1 Tree: http://git-wip-us.apache.org/repos/asf/beam/tree/f54072a1 Diff: http://git-wip-us.apache.org/repos/asf/beam/diff/f54072a1 Branch: refs/heads/maste

[GitHub] beam pull request #3550: [BEAM-2571] CombineTest.testSlidingWindowsCombineWi...

Github user aljoscha closed the pull request at: https://github.com/apache/beam/pull/3550 --- 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 ena

[2/4] beam git commit: [BEAM-2571] Clarify pushedback variable name in DoFnOperator

[BEAM-2571] Clarify pushedback variable name in DoFnOperator Project: http://git-wip-us.apache.org/repos/asf/beam/repo Commit: http://git-wip-us.apache.org/repos/asf/beam/commit/b03c4f07 Tree: http://git-wip-us.apache.org/repos/asf/beam/tree/b03c4f07 Diff: http://git-wip-us.apache.org/repos/asf/b

[jira] [Commented] (BEAM-2571) Flink ValidatesRunner failing CombineTest.testSlidingWindowsCombineWithContext

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

[jira] [Commented] (BEAM-2571) Flink ValidatesRunner failing CombineTest.testSlidingWindowsCombineWithContext

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

[GitHub] beam pull request #3600: [BEAM-2571] CombineTest.testSlidingWindowsCombineWi...

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

[jira] [Assigned] (BEAM-2657) Create Solr IO

[ https://issues.apache.org/jira/browse/BEAM-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismaël Mejía reassigned BEAM-2657: -- Assignee: Cao Manh Dat (was: Davor Bonaci) > Create Solr IO > -- > >

[jira] [Updated] (BEAM-2657) Add Solr IO

[ https://issues.apache.org/jira/browse/BEAM-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismaël Mejía updated BEAM-2657: --- Summary: Add Solr IO (was: Create Solr IO) > Add Solr IO > --- > > Key: BEAM-2

Jenkins build is still unstable: beam_PostCommit_Java_ValidatesRunner_Dataflow #3642

See

Jenkins build is back to stable : beam_PostCommit_Java_ValidatesRunner_Flink #3475

See

[jira] [Created] (BEAM-2669) Kryo serialization exception when DStreams containing non-Kryo-serializable data are cached

Aviem Zur created BEAM-2669: --- Summary: Kryo serialization exception when DStreams containing non-Kryo-serializable data are cached Key: BEAM-2669 URL: https://issues.apache.org/jira/browse/BEAM-2669 Project

[jira] [Commented] (BEAM-2669) Kryo serialization exception when DStreams containing non-Kryo-serializable data are cached

[ https://issues.apache.org/jira/browse/BEAM-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098072#comment-16098072 ] Jean-Baptiste Onofré commented on BEAM-2669: I would be in favor of 2, I don't

[jira] [Commented] (BEAM-2669) Kryo serialization exception when DStreams containing non-Kryo-serializable data are cached

[ https://issues.apache.org/jira/browse/BEAM-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098070#comment-16098070 ] Jean-Baptiste Onofré commented on BEAM-2669: Thanks for the details ! > Kryo s

[jira] [Updated] (BEAM-2669) Kryo serialization exception when DStreams containing non-Kryo-serializable data are cached

[ https://issues.apache.org/jira/browse/BEAM-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aviem Zur updated BEAM-2669: Description: Today, when we detect re-use of a dataset in a pipeline in Spark runner we eagerly cache it to

Jenkins build is still unstable: beam_PostCommit_Java_ValidatesRunner_Spark #2696

See

[jira] [Created] (BEAM-2670) ParDoTest.testPipelineOptionsParameter* validatesRunner tests fail on Spark runner

Etienne Chauchot created BEAM-2670: -- Summary: ParDoTest.testPipelineOptionsParameter* validatesRunner tests fail on Spark runner Key: BEAM-2670 URL: https://issues.apache.org/jira/browse/BEAM-2670 Pr

[jira] [Created] (BEAM-2671) CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner

Etienne Chauchot created BEAM-2671: -- Summary: CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner Key: BEAM-2671 URL: https://issues.apache.org/jira/browse/BEAM-2671 Proj

[jira] [Assigned] (BEAM-2671) CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner

[ https://issues.apache.org/jira/browse/BEAM-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned BEAM-2671: -- Assignee: Jean-Baptiste Onofré (was: Amit Sela) > CreateStreamTest.testFirstEle

[jira] [Commented] (BEAM-2671) CreateStreamTest.testFirstElementLate validatesRunner test fails on Spark runner

[ https://issues.apache.org/jira/browse/BEAM-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098110#comment-16098110 ] Jean-Baptiste Onofré commented on BEAM-2671: We saw that and IMHO, it should be

Jenkins build is still unstable: beam_PostCommit_Java_MavenInstall #4444

See

<    1   2