[jira] [Work logged] (BEAM-7730) Add Flink 1.9 build target and Make FlinkRunner compatible with Flink 1.9
[ https://issues.apache.org/jira/browse/BEAM-7730?focusedWorklogId=305407&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305407 ] ASF GitHub Bot logged work on BEAM-7730: Author: ASF GitHub Bot Created on: 03/Sep/19 05:55 Start Date: 03/Sep/19 05:55 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #9296: WIP: [BEAM-7730] Introduce Flink 1.9 Runner URL: https://github.com/apache/beam/pull/9296#issuecomment-527315098 Hi @dmvk，I creat a hotfix to address the problem. (see: https://github.com/apache/beam/pull/9464) Currently, state keys are encoded as NESTED while the keys in keyselector(KvToByteBufferKeySelector) are encoded as OUTER. This makes the keyGroupId of the same key are different and lead to the test failure. The newest flink version makes this bug more visible. I have check it in my local with your patch. Could you please have look at the changes of the hotfix and double check it whether the hotfix is make sense to you. :) Thank you! Jincheng This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305407) Time Spent: 1h 10m (was: 1h) > Add Flink 1.9 build target and Make FlinkRunner compatible with Flink 1.9 > - > > Key: BEAM-7730 > URL: https://issues.apache.org/jira/browse/BEAM-7730 > Project: Beam > Issue Type: New Feature > Components: runner-flink >Reporter: sunjincheng >Assignee: David Moravek >Priority: Major > Fix For: 2.16.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Apache Flink 1.9 will coming and it's better to add Flink 1.9 build target > and make Flink Runner compatible with Flink 1.9. > I will add the brief changes after the Flink 1.9.0 released. > And I appreciate it if you can leave your suggestions or comments! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-7980) External environment with containerized worker pool
[ https://issues.apache.org/jira/browse/BEAM-7980?focusedWorklogId=305394&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305394 ] ASF GitHub Bot logged work on BEAM-7980: Author: ASF GitHub Bot Created on: 03/Sep/19 04:10 Start Date: 03/Sep/19 04:10 Worklog Time Spent: 10m Work Description: tweise commented on issue #9398: [BEAM-7980] Exactly once artifact retrieval for Python SDK worker pool URL: https://github.com/apache/beam/pull/9398#issuecomment-527296613 @lostluck @aaltay @mxm PTAL since I made a few more changes than those requested to improve the synchronization logic. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305394) Time Spent: 8h 20m (was: 8h 10m) > External environment with containerized worker pool > --- > > Key: BEAM-7980 > URL: https://issues.apache.org/jira/browse/BEAM-7980 > Project: Beam > Issue Type: Improvement > Components: sdk-py-harness >Reporter: Thomas Weise >Assignee: Thomas Weise >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Augment Beam Python docker image and boot.go so that it can be used to launch > BeamFnExternalWorkerPoolServicer. > [https://docs.google.com/document/d/1z3LNrRtr8kkiFHonZ5JJM_L4NWNBBNcqRc_yAf6G0VI/edit#heading=h.lnhm75dhvhi0] > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-7739) Add ValueState in Python sdk
[
https://issues.apache.org/jira/browse/BEAM-7739?focusedWorklogId=305385&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305385
]
ASF GitHub Bot logged work on BEAM-7739:
Author: ASF GitHub Bot
Created on: 03/Sep/19 02:59
Start Date: 03/Sep/19 02:59
Worklog Time Spent: 10m
Work Description: rakeshcusat commented on pull request #9067:
[BEAM-7739] Implement ReadModifyWriteState in Python SDK
URL: https://github.com/apache/beam/pull/9067#discussion_r320076290
##
File path:
runners/core-java/src/main/java/org/apache/beam/runners/core/InMemoryStateInternals.java
##
@@ -166,9 +172,62 @@ public WatermarkHoldState bindWatermark(
}
}
- /** An {@link InMemoryState} implementation of {@link ValueState}. */
+
+ /** An {@link InMemoryState} implementation of {@link ReadModifyWriteState}.
*/
+ public static final class InMemoryReadModifyWrite
+ implements ReadModifyWriteState,
InMemoryState> {
+private final Coder coder;
+
+private boolean isCleared = true;
+private @Nullable T value = null;
+
+public InMemoryReadModifyWrite(Coder coder) {
+ this.coder = coder;
+}
+
+@Override
+public void clear() {
+ // Even though we're clearing we can't remove this from the in-memory
state map, since
+ // other users may already have a handle on this Value.
+ value = null;
+ isCleared = true;
+}
+
+@Override
+public InMemoryReadModifyWrite readLater() {
+ return this;
+}
+
+@Override
+public T read() {
+ return value;
+}
+
+@Override
+public void write(T input) {
+ isCleared = false;
+ this.value = input;
+}
+
+@Override
+public InMemoryReadModifyWrite copy() {
+ InMemoryReadModifyWrite that = new InMemoryReadModifyWrite<>(coder);
+ if (!this.isCleared) {
+that.isCleared = this.isCleared;
+that.value = uncheckedClone(coder, this.value);
+ }
+ return that;
+}
+
+@Override
+public boolean isCleared() {
+ return isCleared;
+}
+ }
+
+ /** An {@link InMemoryState} implementation of {@link ReadModifyWriteState}.
*/
public static final class InMemoryValue
- implements ValueState, InMemoryState> {
+ implements ValueState, InMemoryState> {
Review comment:
This is a good idea, I need to look more closely and consolidate duplicate
code.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305385)
Time Spent: 3.5h (was: 3h 20m)
> Add ValueState in Python sdk
>
>
> Key: BEAM-7739
> URL: https://issues.apache.org/jira/browse/BEAM-7739
> Project: Beam
> Issue Type: New Feature
> Components: sdk-py-core
>Reporter: Rakesh Kumar
>Assignee: Rakesh Kumar
>Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Currently ValueState is missing from Python Sdks but it is existing in Java
> sdks.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (BEAM-7993) portable python precommit is flaky
[
https://issues.apache.org/jira/browse/BEAM-7993?focusedWorklogId=305366&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305366
]
ASF GitHub Bot logged work on BEAM-7993:
Author: ASF GitHub Bot
Created on: 03/Sep/19 01:49
Start Date: 03/Sep/19 01:49
Worklog Time Spent: 10m
Work Description: markflyhigh commented on issue #9460: [BEAM-7993] Run
Portable PreCommit tests sequentially
URL: https://github.com/apache/beam/pull/9460#issuecomment-527273572
Thank you @Hannah-Jiang ! Actually this PR touches `groovy` file so we need
to run seed job before trigger the test job to have Jenkins pickup those
configs first. However, the configs can also be overwritten by other seed jobs.
Two failure examples you mentioned in
https://github.com/apache/beam/pull/9460#issuecomment-526868076 seems still use
old configs. New job should look like
https://builds.apache.org/job/beam_PreCommit_Portable_Python_Phrase/362/
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305366)
Time Spent: 4.5h (was: 4h 20m)
> portable python precommit is flaky
> --
>
> Key: BEAM-7993
> URL: https://issues.apache.org/jira/browse/BEAM-7993
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core, test-failures, testing
>Affects Versions: 2.15.0
>Reporter: Udi Meiri
>Assignee: Mark Liu
>Priority: Major
> Labels: currently-failing
> Fix For: 2.16.0
>
> Attachments: Python_Portable_Precommit.pdf
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> I'm not sure what the root cause is here.
> Example log where
> :sdks:python:test-suites:portable:py35:portableWordCountBatch failed:
> {code}
> 11:51:22 [CHAIN MapPartition (MapPartition at [1]read/Read/Split) -> FlatMap
> (FlatMap at ExtractOutput[0]) (2/2)] ERROR
> org.apache.flink.runtime.operators.BatchTask - Error in task code: CHAIN
> MapPartition (MapPartition at [1]read/Read/Split) -> FlatMap (FlatMap at
> ExtractOutput[0]) (2/2)
> 11:51:22 [CHAIN MapPartition (MapPartition at [1]read/Read/Split) -> FlatMap
> (FlatMap at ExtractOutput[0]) (1/2)] ERROR
> org.apache.flink.runtime.operators.BatchTask - Error in task code: CHAIN
> MapPartition (MapPartition at [1]read/Read/Split) -> FlatMap (FlatMap at
> ExtractOutput[0]) (1/2)
> 11:51:22 [CHAIN MapPartition (MapPartition at
> [2]write/Write/WriteImpl/DoOnce/{FlatMap(),
> Map(decode)}) -> FlatMap (FlatMap at ExtractOutput[0]) (2/2)] ERROR
> org.apache.flink.runtime.operators.BatchTask - Error in task code: CHAIN
> MapPartition (MapPartition at
> [2]write/Write/WriteImpl/DoOnce/{FlatMap(),
> Map(decode)}) -> FlatMap (FlatMap at ExtractOutput[0]) (2/2)
> 11:51:22 [CHAIN MapPartition (MapPartition at
> [2]write/Write/WriteImpl/DoOnce/{FlatMap(),
> Map(decode)}) -> FlatMap (FlatMap at ExtractOutput[0]) (1/2)] ERROR
> org.apache.flink.runtime.operators.BatchTask - Error in task code: CHAIN
> MapPartition (MapPartition at
> [2]write/Write/WriteImpl/DoOnce/{FlatMap(),
> Map(decode)}) -> FlatMap (FlatMap at ExtractOutput[0]) (1/2)
> 11:51:22 java.lang.Exception: The user defined 'open()' method caused an
> exception: java.io.IOException: Received exit code 1 for command 'docker
> inspect -f {{.State.Running}}
> 642c312c335d3881b885873c66917b536e79cff07503fdceaddee5fbeb10bfd1'. stderr:
> Error: No such object:
> 642c312c335d3881b885873c66917b536e79cff07503fdceaddee5fbeb10bfd1
> 11:51:22 at
> org.apache.flink.runtime.operators.BatchTask.run(BatchTask.java:498)
> 11:51:22 at
> org.apache.flink.runtime.operators.BatchTask.invoke(BatchTask.java:368)
> 11:51:22 at org.apache.flink.runtime.taskmanager.Task.run(Task.java:712)
> 11:51:22 at java.lang.Thread.run(Thread.java:748)
> 11:51:22 Caused by:
> org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
> java.io.IOException: Received exit code 1 for command 'docker inspect -f
> {{.State.Running}}
> 642c312c335d3881b885873c66917b536e79cff07503fdceaddee5fbeb10bfd1'. stderr:
> Error: No such object:
> 642c312c335d3881b885873c66917b536e79cff07503fdceaddee5fbeb10bfd1
> 11:51:22 at
> org.apache.beam.vendor.guava.v26_0_jre.com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4966)
> 11:51:22 at
> org.apache.beam.runners.fnexecution.control.DefaultJobBundleFactory$SimpleStageBundleFactory.(DefaultJobBundleFactory.jav
[jira] [Work logged] (BEAM-8019) Support cross-language transforms for DataflowRunner
[ https://issues.apache.org/jira/browse/BEAM-8019?focusedWorklogId=305354&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305354 ] ASF GitHub Bot logged work on BEAM-8019: Author: ASF GitHub Bot Created on: 02/Sep/19 23:51 Start Date: 02/Sep/19 23:51 Worklog Time Spent: 10m Work Description: chamikaramj commented on issue #9390: [BEAM-8019] Several changes to support cross-language transforms on DataflowRunner URL: https://github.com/apache/beam/pull/9390#issuecomment-527259080 R: @robertwb PTAL This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305354) Time Spent: 20m (was: 10m) > Support cross-language transforms for DataflowRunner > > > Key: BEAM-8019 > URL: https://issues.apache.org/jira/browse/BEAM-8019 > Project: Beam > Issue Type: New Feature > Components: sdk-py-core >Reporter: Chamikara Jayalath >Assignee: Chamikara Jayalath >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > This is to capture the Beam changes needed for this task. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-4087) Gradle build does not allow to overwrite versions of provided dependencies
[ https://issues.apache.org/jira/browse/BEAM-4087?focusedWorklogId=305306&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305306 ] ASF GitHub Bot logged work on BEAM-4087: Author: ASF GitHub Bot Created on: 02/Sep/19 19:01 Start Date: 02/Sep/19 19:01 Worklog Time Spent: 10m Work Description: stale[bot] commented on issue #8255: [BEAM-4087] implement configurable dependency versions URL: https://github.com/apache/beam/pull/8255#issuecomment-527225107 This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the d...@beam.apache.org list. Thank you for your contributions. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305306) Time Spent: 4.5h (was: 4h 20m) > Gradle build does not allow to overwrite versions of provided dependencies > -- > > Key: BEAM-4087 > URL: https://issues.apache.org/jira/browse/BEAM-4087 > Project: Beam > Issue Type: Sub-task > Components: build-system >Affects Versions: 2.5.0 >Reporter: Ismaël Mejía >Assignee: Michael Luckey >Priority: Major > Time Spent: 4.5h > Remaining Estimate: 0h > > In order to test modules with provided dependencies in maven we can execute > for example for Kafka `mvn verify -Prelease -Dkafka.clients.version=0.9.0.1 > -pl 'sdks/java/io/kafka'` However we don't have an equivalent way to do this > with gradle because the version of the dependencies are defined locally and > not in the gradle.properties. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-7605) Provide a way for user code to read dataflow runner stats
[ https://issues.apache.org/jira/browse/BEAM-7605?focusedWorklogId=305260&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305260 ] ASF GitHub Bot logged work on BEAM-7605: Author: ASF GitHub Bot Created on: 02/Sep/19 15:50 Start Date: 02/Sep/19 15:50 Worklog Time Spent: 10m Work Description: steveniemitz commented on pull request #8913: [BEAM-7605] Allow user-code to read counters from the dataflow worker URL: https://github.com/apache/beam/pull/8913 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305260) Time Spent: 3h (was: 2h 50m) > Provide a way for user code to read dataflow runner stats > - > > Key: BEAM-7605 > URL: https://issues.apache.org/jira/browse/BEAM-7605 > Project: Beam > Issue Type: Improvement > Components: runner-dataflow >Reporter: Steve Niemitz >Assignee: Steve Niemitz >Priority: Major > Time Spent: 3h > Remaining Estimate: 0h > > The dataflow runner collects (and publishes to the dataflow service) a large > number of useful stats. While these can be polled from the dataflow service > via its API, there are a few downsides to this: > * it requires another process to poll and collect the stats > * the stats are aggregated across all workers, so per-worker stats are lost > It would be simple to provide a hook to allow users to receive stats updates > as well, and then do whatever they want with them. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-7605) Provide a way for user code to read dataflow runner stats
[ https://issues.apache.org/jira/browse/BEAM-7605?focusedWorklogId=305259&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305259 ] ASF GitHub Bot logged work on BEAM-7605: Author: ASF GitHub Bot Created on: 02/Sep/19 15:50 Start Date: 02/Sep/19 15:50 Worklog Time Spent: 10m Work Description: steveniemitz commented on issue #8913: [BEAM-7605] Allow user-code to read counters from the dataflow worker URL: https://github.com/apache/beam/pull/8913#issuecomment-527191057 I'm just going to close this for now, I don't mind maintaining my own fork for the time being. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305259) Time Spent: 2h 50m (was: 2h 40m) > Provide a way for user code to read dataflow runner stats > - > > Key: BEAM-7605 > URL: https://issues.apache.org/jira/browse/BEAM-7605 > Project: Beam > Issue Type: Improvement > Components: runner-dataflow >Reporter: Steve Niemitz >Assignee: Steve Niemitz >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > The dataflow runner collects (and publishes to the dataflow service) a large > number of useful stats. While these can be polled from the dataflow service > via its API, there are a few downsides to this: > * it requires another process to poll and collect the stats > * the stats are aggregated across all workers, so per-worker stats are lost > It would be simple to provide a hook to allow users to receive stats updates > as well, and then do whatever they want with them. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-5428) Implement cross-bundle state caching.
[ https://issues.apache.org/jira/browse/BEAM-5428?focusedWorklogId=305250&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305250 ] ASF GitHub Bot logged work on BEAM-5428: Author: ASF GitHub Bot Created on: 02/Sep/19 15:46 Start Date: 02/Sep/19 15:46 Worklog Time Spent: 10m Work Description: mxm commented on issue #9374: [BEAM-5428] Implement Runner support for cache tokens URL: https://github.com/apache/beam/pull/9374#issuecomment-527189955 >How do you imagine cache invalidation would happen (I'm asking because I wonder whether we should be exposing invalidateCacheToken APIs as part of the shared runner fn-execution code)? In my mind, the Runner simply redeploys the operator in case of a failure and that discards all its ephemeral state (e.g. cache tokens). Only state persisted in the Runner's state backend will be restored after a failure. I know this model works for Flink and Spark. If such a model works for all Runners, then we could indeed remove the `invalidateCacheToken()` method from the user state handler. So I'll remove the invalidation logic from `BagUserStateHandler`. Are you also suggesting, we should remove it from `StateRequestHandler` as well? Then nothing would be exposed in fn-execution. All the invalidation logic would be inside the state handler implementations. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305250) Time Spent: 12h 50m (was: 12h 40m) > Implement cross-bundle state caching. > - > > Key: BEAM-5428 > URL: https://issues.apache.org/jira/browse/BEAM-5428 > Project: Beam > Issue Type: Improvement > Components: sdk-py-harness >Reporter: Robert Bradshaw >Assignee: Rakesh Kumar >Priority: Major > Time Spent: 12h 50m > Remaining Estimate: 0h > > Tech spec: > [https://docs.google.com/document/d/1BOozW0bzBuz4oHJEuZNDOHdzaV5Y56ix58Ozrqm2jFg/edit#heading=h.7ghoih5aig5m] > Relevant document: > [https://docs.google.com/document/d/1ltVqIW0XxUXI6grp17TgeyIybk3-nDF8a0-Nqw-s9mY/edit#|https://docs.google.com/document/d/1ltVqIW0XxUXI6grp17TgeyIybk3-nDF8a0-Nqw-s9mY/edit] > Mailing list link: > [https://lists.apache.org/thread.html/caa8d9bc6ca871d13de2c5e6ba07fdc76f85d26497d95d90893aa1f6@%3Cdev.beam.apache.org%3E] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (BEAM-8115) Overwrite portable Flink application jar pipeline options at runtime
[ https://issues.apache.org/jira/browse/BEAM-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated BEAM-8115: - Status: Open (was: Triage Needed) > Overwrite portable Flink application jar pipeline options at runtime > > > Key: BEAM-8115 > URL: https://issues.apache.org/jira/browse/BEAM-8115 > Project: Beam > Issue Type: New Feature > Components: runner-flink >Reporter: Kyle Weaver >Assignee: Kyle Weaver >Priority: Major > > In the first iteration of portable Flink application jars, all pipeline > options are set at job creation time and cannot be later modified at runtime. > There should be a way to pass arguments to the jar to write/overwrite > pipeline options. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (BEAM-8102) Portable Flink and Spark failing testSideInputAnnotation[WithMultipleSideInputs]
[ https://issues.apache.org/jira/browse/BEAM-8102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved BEAM-8102. -- Fix Version/s: Not applicable Assignee: Reuven Lax Resolution: Fixed > Portable Flink and Spark failing > testSideInputAnnotation[WithMultipleSideInputs] > > > Key: BEAM-8102 > URL: https://issues.apache.org/jira/browse/BEAM-8102 > Project: Beam > Issue Type: Bug > Components: java-fn-execution, runner-flink, runner-spark >Reporter: Kyle Weaver >Assignee: Reuven Lax >Priority: Major > Labels: portability-flink, portability-spark > Fix For: Not applicable > > Time Spent: 1h 20m > Remaining Estimate: 0h > > [https://builds.apache.org/job/beam_PostCommit_Java_PVR_Spark_Batch/] > [https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/] > java.lang.AssertionError: Pipeline did not succeed. Expected: is but: > was -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (BEAM-8121) Messages are not distributed per machines when consuming from Kafka topic with 1 partition
[ https://issues.apache.org/jira/browse/BEAM-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920907#comment-16920907 ] Alexey Romanenko commented on BEAM-8121: Thank you for additional details. Could you also post a code of your pipeline for reference, if it's possible? > Messages are not distributed per machines when consuming from Kafka topic > with 1 partition > -- > > Key: BEAM-8121 > URL: https://issues.apache.org/jira/browse/BEAM-8121 > Project: Beam > Issue Type: Bug > Components: io-java-kafka >Affects Versions: 2.14.0 >Reporter: TJ >Priority: Major > > Messages are consumed from Kafka using KafkaIO. Each kafka topic contains > only 1 partition. (That means that messages can be consumed only by one > Consumer per 1 consumer group) > When backlog of topic grows and system scales from 1 to X machines, all the > messages seems to be executed on the same machine on which they are read. > Due to that message throughput doesn't increase comparing X machines to 1 > machine. If one machine was reading 2K messages per s, X machines will be > reading the same amount. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (BEAM-8121) Messages are not distributed per machines when consuming from Kafka topic with 1 partition
[ https://issues.apache.org/jira/browse/BEAM-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Romanenko updated BEAM-8121: --- Status: Open (was: Triage Needed) > Messages are not distributed per machines when consuming from Kafka topic > with 1 partition > -- > > Key: BEAM-8121 > URL: https://issues.apache.org/jira/browse/BEAM-8121 > Project: Beam > Issue Type: Bug > Components: io-java-kafka >Affects Versions: 2.14.0 >Reporter: TJ >Priority: Major > > Messages are consumed from Kafka using KafkaIO. Each kafka topic contains > only 1 partition. (That means that messages can be consumed only by one > Consumer per 1 consumer group) > When backlog of topic grows and system scales from 1 to X machines, all the > messages seems to be executed on the same machine on which they are read. > Due to that message throughput doesn't increase comparing X machines to 1 > machine. If one machine was reading 2K messages per s, X machines will be > reading the same amount. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (BEAM-8121) Messages are not distributed per machines when consuming from Kafka topic with 1 partition
[ https://issues.apache.org/jira/browse/BEAM-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920886#comment-16920886 ] TJ edited comment on BEAM-8121 at 9/2/19 2:03 PM: -- I use Dataflow runner. I tried Reshuffle.viaRandomKey(), it worked quite poorly and had side effects: * Pipeline started to have constant lag (2-3 min) on Reshuffle step. * CPU usage increased from 20-30% to almost 80%. On n1-standard-4 ([https://cloud.google.com/compute/docs/machine-types]). * With single machine it was consuming less messages. 1 machine without reshuffle step ±1500message/s, 1 machine with reshuffle step ±450message/s. When it scaled to 5 it was consuming the same 1500message/s as without the step. I approached google support and they advised do not use Reshuffle step at all. Cause it's deprecated and not stable. I assume if I would use more powerful machines and the higher number of them as 5 it would theoretically reach the max throughput, but it would be really costly for such small message throughput. One more thing to mention. I did the throughput test for Kafka Standalone app and Dataflow pipeline. They were consuming from the same topic with 1 partition. Message size 1.3KB. Results: Standalone kafka client was consuming 5000 message/s Dataflow pipeline with few empty tasks 3200message/s Dataflow pipeline with normal tasks what manipulates data 1500message/s was (Author: taujan): I use Dataflow runner. I tried Reshuffle.viaRandomKey(), it worked quite poorly and had side effects: * Pipeline started to have constant lag (2-3 min) on Reshuffle step. * CPU usage increased from 20-30% to almost 80%. On n1-standard-4 ([https://cloud.google.com/compute/docs/machine-types]). * With single machine it was consuming less messages. 1 machine without reshuffle step ±1500message/s, 1 machine with reshuffle step ±450message/s. When it scaled to 5 it was consuming the same 1500message/s as without the step. I approached google support and they advised do not use Reshuffle step at all. Cause it's deprecated and not stable. One more thing to mention. I did the throughput test for Kafka Standalone app and Dataflow pipeline. They were consuming from the same topic with 1 partition. Results: Standalone kafka client was consuming 4500 message/s Dataflow pipeline with few empty tasks 3200message/s Dataflow pipeline with normal tasks what manipulates data 1500message/s > Messages are not distributed per machines when consuming from Kafka topic > with 1 partition > -- > > Key: BEAM-8121 > URL: https://issues.apache.org/jira/browse/BEAM-8121 > Project: Beam > Issue Type: Bug > Components: io-java-kafka >Affects Versions: 2.14.0 >Reporter: TJ >Priority: Major > > Messages are consumed from Kafka using KafkaIO. Each kafka topic contains > only 1 partition. (That means that messages can be consumed only by one > Consumer per 1 consumer group) > When backlog of topic grows and system scales from 1 to X machines, all the > messages seems to be executed on the same machine on which they are read. > Due to that message throughput doesn't increase comparing X machines to 1 > machine. If one machine was reading 2K messages per s, X machines will be > reading the same amount. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (BEAM-8121) Messages are not distributed per machines when consuming from Kafka topic with 1 partition
[ https://issues.apache.org/jira/browse/BEAM-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920886#comment-16920886 ] TJ commented on BEAM-8121: -- I use Dataflow runner. I tried Reshuffle.viaRandomKey(), it worked quite poorly and had side effects: * Pipeline started to have constant lag (2-3 min) on Reshuffle step. * CPU usage increased from 20-30% to almost 80%. On n1-standard-4 ([https://cloud.google.com/compute/docs/machine-types]). * With single machine it was consuming less messages. 1 machine without reshuffle step ±1500message/s, 1 machine with reshuffle step ±450message/s. When it scaled to 5 it was consuming the same 1500message/s as without the step. I approached google support and they advised do not use Reshuffle step at all. Cause it's deprecated and not stable. One more thing to mention. I did the throughput test for Kafka Standalone app and Dataflow pipeline. They were consuming from the same topic with 1 partition. Results: Standalone kafka client was consuming 4500 message/s Dataflow pipeline with few empty tasks 3200message/s Dataflow pipeline with normal tasks what manipulates data 1500message/s > Messages are not distributed per machines when consuming from Kafka topic > with 1 partition > -- > > Key: BEAM-8121 > URL: https://issues.apache.org/jira/browse/BEAM-8121 > Project: Beam > Issue Type: Bug > Components: io-java-kafka >Affects Versions: 2.14.0 >Reporter: TJ >Priority: Major > > Messages are consumed from Kafka using KafkaIO. Each kafka topic contains > only 1 partition. (That means that messages can be consumed only by one > Consumer per 1 consumer group) > When backlog of topic grows and system scales from 1 to X machines, all the > messages seems to be executed on the same machine on which they are read. > Due to that message throughput doesn't increase comparing X machines to 1 > machine. If one machine was reading 2K messages per s, X machines will be > reading the same amount. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (BEAM-8121) Messages are not distributed per machines when consuming from Kafka topic with 1 partition
[
https://issues.apache.org/jira/browse/BEAM-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920851#comment-16920851
]
Alexey Romanenko commented on BEAM-8121:
I guess it could be caused by fusion when messages, consumed by the same
consumer, will be processed on the same worker. Which runner do you use? Did
you try to use {{Reshuffle.viaRandomKey()}} to break a fusion?
> Messages are not distributed per machines when consuming from Kafka topic
> with 1 partition
> --
>
> Key: BEAM-8121
> URL: https://issues.apache.org/jira/browse/BEAM-8121
> Project: Beam
> Issue Type: Bug
> Components: io-java-kafka
>Affects Versions: 2.14.0
>Reporter: TJ
>Priority: Major
>
> Messages are consumed from Kafka using KafkaIO. Each kafka topic contains
> only 1 partition. (That means that messages can be consumed only by one
> Consumer per 1 consumer group)
> When backlog of topic grows and system scales from 1 to X machines, all the
> messages seems to be executed on the same machine on which they are read.
> Due to that message throughput doesn't increase comparing X machines to 1
> machine. If one machine was reading 2K messages per s, X machines will be
> reading the same amount.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (BEAM-8128) Don't deprecate Read for Impulse
Romain Manni-Bucau created BEAM-8128: Summary: Don't deprecate Read for Impulse Key: BEAM-8128 URL: https://issues.apache.org/jira/browse/BEAM-8128 Project: Beam Issue Type: Bug Components: runner-core, sdk-java-core Affects Versions: 2.15.0 Reporter: Romain Manni-Bucau In last beam release, Read.Bounded and Read.Unbounded are deprecated and beam tends to move to Impulse usage. This is a huge breaking change since users can't rely on custom pre-runner pipeline visitor to instrument their pipelines anymore or even identify the transform accurately anymore. This issue is about ensure that SDF or not Read.Bounded and Read.Unbounded is a stable transform matcher and can still be used by user code to identify inputs. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (BEAM-5750) Beam Dependency Update Request: javax.servlet:javax.servlet-api
[ https://issues.apache.org/jira/browse/BEAM-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-5750: Description: - 2018-10-15 12:13:14.253682 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-22 12:13:20.677351 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-29 12:17:03.954722 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-05 12:14:50.209888 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-12 12:14:50.401239 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-19 12:15:31.652290 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-26 12:14:29.396363 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-03 12:14:52.265627 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-10 12:17:21.331309 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-17 12:17:42.365110 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-31 15:24:01.296226 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-07 12:27:13.634593 - Please consider upgrading the dependency javax.servlet:javax.servlet-api. The current version is 3.1.0. The latest version is 4.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify
[jira] [Updated] (BEAM-8002) Beam Dependency Update Request: Gradle:
[ https://issues.apache.org/jira/browse/BEAM-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-8002: Description: - 2019-08-19 12:04:19.192688 - Please consider upgrading the dependency Gradle:. The current version is 5.2.1. The latest version is 5.6 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-26 12:04:17.802062 - Please consider upgrading the dependency Gradle:. The current version is 5.2.1. The latest version is 5.6 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-09-02 12:04:53.057461 - Please consider upgrading the dependency Gradle:. The current version is 5.2.1. The latest version is 5.6.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. was: - 2019-08-19 12:04:19.192688 - Please consider upgrading the dependency Gradle:. The current version is 5.2.1. The latest version is 5.6 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-26 12:04:17.802062 - Please consider upgrading the dependency Gradle:. The current version is 5.2.1. The latest version is 5.6 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. > Beam Dependency Update Request: Gradle: > --- > > Key: BEAM-8002 > URL: https://issues.apache.org/jira/browse/BEAM-8002 > Project: Beam > Issue Type: Sub-task > Components: dependencies >Reporter: Beam JIRA Bot >Priority: Major > > - 2019-08-19 12:04:19.192688 > - > Please consider upgrading the dependency Gradle:. > The current version is 5.2.1. The latest version is 5.6 > cc: > Please refer to [Beam Dependency Guide > |https://beam.apache.org/contribute/dependencies/]for more information. > Do Not Modify The Description Above. > - 2019-08-26 12:04:17.802062 > - > Please consider upgrading the dependency Gradle:. > The current version is 5.2.1. The latest version is 5.6 > cc: > Please refer to [Beam Dependency Guide > |https://beam.apache.org/contribute/dependencies/]for more information. > Do Not Modify The Description Above. > - 2019-09-02 12:04:53.057461 > - > Please consider upgrading the dependency Gradle:. > The current version is 5.2.1. The latest version is 5.6.1 > cc: > Please refer to [Beam Dependency Guide > |https://beam.apache.org/contribute/dependencies/]for more information. > Do Not Modify The Description Above. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (BEAM-5748) Beam Dependency Update Request: org.conscrypt:conscrypt-openjdk
[ https://issues.apache.org/jira/browse/BEAM-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-5748: Description: - 2018-10-15 12:11:29.496210 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-22 12:11:12.117107 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-29 12:13:29.155766 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-05 12:12:12.225263 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-12 12:12:03.483941 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-19 12:12:49.618981 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-26 12:11:54.540783 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-03 12:12:15.486522 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-10 12:14:35.731081 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-17 12:15:07.608265 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-31 15:21:22.979404 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-07 12:24:30.102231 - Please consider upgrading the dependency org.conscrypt:conscrypt-openjdk. The current version is 1.1.3. The latest version is 1.4.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify
[jira] [Updated] (BEAM-5753) Beam Dependency Update Request: org.eclipse.jetty:jetty-servlet
[ https://issues.apache.org/jira/browse/BEAM-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-5753: Description: - 2018-10-15 12:13:19.256622 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-22 12:13:32.240729 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-29 12:17:15.388249 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-05 12:15:02.810121 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-12 12:15:02.741564 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-19 12:15:44.462009 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-26 12:14:43.766710 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-03 12:15:09.151091 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-10 12:17:38.451204 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-17 12:17:59.925429 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-31 15:24:18.611955 - Please consider upgrading the dependency org.eclipse.jetty:jetty-servlet. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-07 12:27:30.751791 - Please consider upgrading the dependency org.eclipse.jetty:je
[jira] [Updated] (BEAM-5752) Beam Dependency Update Request: org.eclipse.jetty:jetty-server
[ https://issues.apache.org/jira/browse/BEAM-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-5752: Description: - 2018-10-15 12:13:17.575546 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-22 12:13:26.908573 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-29 12:17:10.104039 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-05 12:14:56.891103 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-12 12:14:57.086704 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.12.RC2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-19 12:15:38.454968 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-26 12:14:38.329092 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-03 12:15:03.778648 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-10 12:17:33.026807 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-17 12:17:54.249911 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-31 15:24:13.071360 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server. The current version is 9.2.10.v20150310. The latest version is 9.4.14.v20181114 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-07 12:27:25.376755 - Please consider upgrading the dependency org.eclipse.jetty:jetty-server.
[jira] [Updated] (BEAM-7369) Beam Dependency Update Request: mock
[ https://issues.apache.org/jira/browse/BEAM-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-7369: Description: - 2019-05-20 16:37:42.331317 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-17 12:32:01.319061 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-24 12:02:34.500201 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-01 12:03:46.078139 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-08 12:02:33.351570 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-15 12:02:47.637435 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-22 12:03:10.835914 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-29 12:04:50.359555 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-05 12:02:38.989136 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-12 12:03:38.282286 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-19 12:02:30.405376 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-26 12:02:24.272597 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-09-02 12:03:07.834005 - Please consider upgrading the dependency mock. The current version is 2.0.0. The latest version is 3.0.5 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/
[jira] [Updated] (BEAM-6951) Beam Dependency Update Request: com.github.spotbugs:spotbugs-annotations
[ https://issues.apache.org/jira/browse/BEAM-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-6951: Description: - 2019-04-01 12:15:05.460427 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-08 12:15:37.305259 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-15 12:35:52.817108 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-22 12:13:25.261372 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-05-20 16:39:18.034675 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-05-20 16:54:09.180503 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-05-20 17:37:40.326607 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-05-27 12:06:48.236836 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-03 12:04:13.166255 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-10 12:04:08.241217 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-17 12:33:32.545061 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current version is 3.1.11. The latest version is 4.0.0-beta2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-24 12:04:02.498856 - Please consider upgrading the dependency com.github.spotbugs:spotbugs-annotations. The current ver
[jira] [Updated] (BEAM-6645) Beam Dependency Update Request: com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin
[ https://issues.apache.org/jira/browse/BEAM-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-6645: Description: - 2019-02-11 12:12:17.710870 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.20.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-02-18 12:22:38.110512 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.20.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-02-25 12:12:13.220144 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.20.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-03-04 12:13:34.975335 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-03-11 12:13:20.550078 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-03-25 04:18:13.860760 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-01 12:09:02.686241 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-08 12:11:15.303458 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-15 12:30:47.279374 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-04-22 12:08:36.647085 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-05-20 16:38:23.480410 - Please consider upgrading the dependency com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin. The current version is 0.17.0. The latest version is 0.21.0 cc: Please refer to [Beam Dependency Guide |ht
[jira] [Updated] (BEAM-7792) Beam Dependency Update Request: com.github.spotbugs:spotbugs
[ https://issues.apache.org/jira/browse/BEAM-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-7792: Description: - 2019-07-22 12:15:41.216793 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-29 12:06:22.055418 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-05 12:03:56.940731 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-12 12:05:04.611973 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-19 12:03:13.035336 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.12. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-26 12:02:56.981076 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.12. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-09-02 12:03:52.780365 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.12. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. was: - 2019-07-22 12:15:41.216793 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-29 12:06:22.055418 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-05 12:03:56.940731 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-12 12:05:04.611973 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.10. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-19 12:03:13.035336 - Please consider upgrading the dependency com.github.spotbugs:spotbugs. The current version is 3.1.12. The latest version is 4.0.0-beta3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/depen
[jira] [Updated] (BEAM-7370) Beam Dependency Update Request: Sphinx
[ https://issues.apache.org/jira/browse/BEAM-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-7370: Description: - 2019-05-20 16:38:07.937770 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.0.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-17 12:32:27.855338 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.1 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-06-24 12:02:59.052884 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-01 12:04:13.113613 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-08 12:03:15.091005 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-15 12:03:09.406918 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-22 12:03:31.157859 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-07-29 12:05:13.023604 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-05 12:03:03.242767 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-12 12:04:01.647619 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.1.2 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-19 12:02:52.342008 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.2.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-08-26 12:02:44.918642 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.2.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-09-02 12:03:28.319578 - Please consider upgrading the dependency Sphinx. The current version is 1.8.5. The latest version is 2.2.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.or
[jira] [Updated] (BEAM-6089) Beam Dependency Update Request: oauth2client
[ https://issues.apache.org/jira/browse/BEAM-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-6089: Description: - 2018-11-19 12:11:53.801885 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-26 12:10:31.359164 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-03 12:11:18.194090 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-10 12:13:40.021791 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-17 12:12:09.88 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-31 15:20:14.935936 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-07 12:23:14.664558 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-14 12:12:14.081917 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-21 12:18:38.928775 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-01-28 12:10:22.371989 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-02-04 12:11:00.277439 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-02-11 12:11:25.422782 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2019-02-18 12:21:52.210498 - Please consider upgrading the dependency oauth2client. The current version is 3.0.0. The latest version is 4.1.3
[jira] [Created] (BEAM-8127) Beam Dependency Update Request: google-cloud-bigtable
Beam JIRA Bot created BEAM-8127: --- Summary: Beam Dependency Update Request: google-cloud-bigtable Key: BEAM-8127 URL: https://issues.apache.org/jira/browse/BEAM-8127 Project: Beam Issue Type: Bug Components: dependencies Reporter: Beam JIRA Bot - 2019-09-02 12:02:43.329304 - Please consider upgrading the dependency google-cloud-bigtable. The current version is 0.32.2. The latest version is 1.0.0 cc: Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (BEAM-5539) Beam Dependency Update Request: google-cloud-pubsub
[ https://issues.apache.org/jira/browse/BEAM-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Beam JIRA Bot updated BEAM-5539: Description: - 2018-10-01 19:17:59.633423 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.26.0. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-08 12:11:22.339342 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-15 12:10:17.795498 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.26.0. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-22 12:10:36.369849 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-10-29 12:12:47.703482 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-05 12:11:03.025934 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-12 12:11:07.165089 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-19 12:11:33.666549 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-11-26 12:09:57.098788 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.38.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-03 12:10:44.692853 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.39.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-10 12:10:31.139202 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.39.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/contribute/dependencies/]for more information. Do Not Modify The Description Above. - 2018-12-17 12:12:00.165700 - Please consider upgrading the dependency google-cloud-pubsub. The current version is 0.35.4. The latest version is 0.39.0 cc: [~markflyhigh], Please refer to [Beam Dependency Guide |https://beam.apache.org/c
[jira] [Work logged] (BEAM-7520) DirectRunner timers are not strictly time ordered
[ https://issues.apache.org/jira/browse/BEAM-7520?focusedWorklogId=305124&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305124 ] ASF GitHub Bot logged work on BEAM-7520: Author: ASF GitHub Bot Created on: 02/Sep/19 09:59 Start Date: 02/Sep/19 09:59 Worklog Time Spent: 10m Work Description: je-ik commented on issue #9190: [BEAM-7520] Fix timer firing order in DirectRunner URL: https://github.com/apache/beam/pull/9190#issuecomment-527086557 For clarity, it is [this one](https://github.com/apache/beam/pull/9190/files#diff-68ed88cc25171e30985dda4534e68c9bR3184) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305124) Time Spent: 9h 20m (was: 9h 10m) > DirectRunner timers are not strictly time ordered > - > > Key: BEAM-7520 > URL: https://issues.apache.org/jira/browse/BEAM-7520 > Project: Beam > Issue Type: Bug > Components: runner-direct >Affects Versions: 2.13.0 >Reporter: Jan Lukavský >Assignee: Jan Lukavský >Priority: Major > Time Spent: 9h 20m > Remaining Estimate: 0h > > Let's suppose we have the following situation: > - statful ParDo with two timers - timerA and timerB > - timerA is set for window.maxTimestamp() + 1 > - timerB is set anywhere between timerB.timestamp > - input watermark moves to BoundedWindow.TIMESTAMP_MAX_VALUE > Then the order of timers is as follows (correct): > - timerB > - timerA > But, if timerB sets another timer (say for timerB.timestamp + 1), then the > order of timers will be: > - timerB (timerB.timestamp) > - timerA (BoundedWindow.TIMESTAMP_MAX_VALUE) > - timerB (timerB.timestamp + 1) > Which is not ordered by timestamp. The reason for this is that when the input > watermark update is evaluated, the WatermarkManager,extractFiredTimers() will > produce both timerA and timerB. That would be correct, but when timerB sets > another timer, that breaks this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-7520) DirectRunner timers are not strictly time ordered
[ https://issues.apache.org/jira/browse/BEAM-7520?focusedWorklogId=305123&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305123 ] ASF GitHub Bot logged work on BEAM-7520: Author: ASF GitHub Bot Created on: 02/Sep/19 09:58 Start Date: 02/Sep/19 09:58 Worklog Time Spent: 10m Work Description: je-ik commented on issue #9190: [BEAM-7520] Fix timer firing order in DirectRunner URL: https://github.com/apache/beam/pull/9190#issuecomment-527086028 @kennknowles @reuvenlax The added @ValidatesRunner fails on Dataflow. It looks to me, that it should pass, but cannot tell for sure. Can you check this? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 305123) Time Spent: 9h 10m (was: 9h) > DirectRunner timers are not strictly time ordered > - > > Key: BEAM-7520 > URL: https://issues.apache.org/jira/browse/BEAM-7520 > Project: Beam > Issue Type: Bug > Components: runner-direct >Affects Versions: 2.13.0 >Reporter: Jan Lukavský >Assignee: Jan Lukavský >Priority: Major > Time Spent: 9h 10m > Remaining Estimate: 0h > > Let's suppose we have the following situation: > - statful ParDo with two timers - timerA and timerB > - timerA is set for window.maxTimestamp() + 1 > - timerB is set anywhere between timerB.timestamp > - input watermark moves to BoundedWindow.TIMESTAMP_MAX_VALUE > Then the order of timers is as follows (correct): > - timerB > - timerA > But, if timerB sets another timer (say for timerB.timestamp + 1), then the > order of timers will be: > - timerB (timerB.timestamp) > - timerA (BoundedWindow.TIMESTAMP_MAX_VALUE) > - timerB (timerB.timestamp + 1) > Which is not ordered by timestamp. The reason for this is that when the input > watermark update is evaluated, the WatermarkManager,extractFiredTimers() will > produce both timerA and timerB. That would be correct, but when timerB sets > another timer, that breaks this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (BEAM-8113) FlinkRunner: Stage files from context classloader
[
https://issues.apache.org/jira/browse/BEAM-8113?focusedWorklogId=305121&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305121
]
ASF GitHub Bot logged work on BEAM-8113:
Author: ASF GitHub Bot
Created on: 02/Sep/19 09:54
Start Date: 02/Sep/19 09:54
Worklog Time Spent: 10m
Work Description: je-ik commented on issue #9451: [BEAM-8113] Stage files
from context classloader
URL: https://github.com/apache/beam/pull/9451#issuecomment-527084901
Run Flink ValidatesRunner
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305121)
Time Spent: 3h 20m (was: 3h 10m)
> FlinkRunner: Stage files from context classloader
> -
>
> Key: BEAM-8113
> URL: https://issues.apache.org/jira/browse/BEAM-8113
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
>Reporter: Jan Lukavský
>Assignee: Jan Lukavský
>Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Currently, only files from {{FlinkRunner.class.getClassLoader()}} are staged
> by default. Add also files from
> {{Thread.currentThread().getContextClassLoader()}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (BEAM-8113) FlinkRunner: Stage files from context classloader
[
https://issues.apache.org/jira/browse/BEAM-8113?focusedWorklogId=305122&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305122
]
ASF GitHub Bot logged work on BEAM-8113:
Author: ASF GitHub Bot
Created on: 02/Sep/19 09:54
Start Date: 02/Sep/19 09:54
Worklog Time Spent: 10m
Work Description: je-ik commented on issue #9451: [BEAM-8113] Stage files
from context classloader
URL: https://github.com/apache/beam/pull/9451#issuecomment-527084954
Run Spark ValidatesRunner
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305122)
Time Spent: 3.5h (was: 3h 20m)
> FlinkRunner: Stage files from context classloader
> -
>
> Key: BEAM-8113
> URL: https://issues.apache.org/jira/browse/BEAM-8113
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
>Reporter: Jan Lukavský
>Assignee: Jan Lukavský
>Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Currently, only files from {{FlinkRunner.class.getClassLoader()}} are staged
> by default. Add also files from
> {{Thread.currentThread().getContextClassLoader()}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (BEAM-8113) FlinkRunner: Stage files from context classloader
[
https://issues.apache.org/jira/browse/BEAM-8113?focusedWorklogId=305120&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305120
]
ASF GitHub Bot logged work on BEAM-8113:
Author: ASF GitHub Bot
Created on: 02/Sep/19 09:54
Start Date: 02/Sep/19 09:54
Worklog Time Spent: 10m
Work Description: je-ik commented on issue #9451: [BEAM-8113] Stage files
from context classloader
URL: https://github.com/apache/beam/pull/9451#issuecomment-527084771
Run Dataflow ValidatesRunner
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305120)
Time Spent: 3h 10m (was: 3h)
> FlinkRunner: Stage files from context classloader
> -
>
> Key: BEAM-8113
> URL: https://issues.apache.org/jira/browse/BEAM-8113
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
>Reporter: Jan Lukavský
>Assignee: Jan Lukavský
>Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Currently, only files from {{FlinkRunner.class.getClassLoader()}} are staged
> by default. Add also files from
> {{Thread.currentThread().getContextClassLoader()}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (BEAM-8114) Chicago Taxi on Dataflow is failing
[
https://issues.apache.org/jira/browse/BEAM-8114?focusedWorklogId=305090&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305090
]
ASF GitHub Bot logged work on BEAM-8114:
Author: ASF GitHub Bot
Created on: 02/Sep/19 08:27
Start Date: 02/Sep/19 08:27
Worklog Time Spent: 10m
Work Description: mwalenia commented on issue #9456: [BEAM-8114] Fix
failing Chicago Taxi Example job on Jenkins
URL: https://github.com/apache/beam/pull/9456#issuecomment-527054147
Run Chicago Taxi on Dataflow
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305090)
Time Spent: 1h 20m (was: 1h 10m)
> Chicago Taxi on Dataflow is failing
> ---
>
> Key: BEAM-8114
> URL: https://issues.apache.org/jira/browse/BEAM-8114
> Project: Beam
> Issue Type: Bug
> Components: testing
>Reporter: Kamil Wasilewski
>Assignee: Michal Walenia
>Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> An exception is being raised when publishing metrics:
>
> {code:java}
> 16:48:57 value = self._prepare_runtime_metrics(runtime_list)
> 16:48:57 File
> "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python_Chicago_Taxi_Dataflow/src/sdks/python/apache_beam/testing/load_tests/load_test_metrics_utils.py",
> line 317, in _prepare_runtime_metrics
> 16:48:57 min_value = min(min_values)
> 16:48:57 ValueError: min() arg is an empty sequence
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (BEAM-8114) Chicago Taxi on Dataflow is failing
[
https://issues.apache.org/jira/browse/BEAM-8114?focusedWorklogId=305088&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305088
]
ASF GitHub Bot logged work on BEAM-8114:
Author: ASF GitHub Bot
Created on: 02/Sep/19 08:16
Start Date: 02/Sep/19 08:16
Worklog Time Spent: 10m
Work Description: mwalenia commented on issue #9456: [BEAM-8114] Fix
failing Chicago Taxi Example job on Jenkins
URL: https://github.com/apache/beam/pull/9456#issuecomment-527049937
Run seed job
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305088)
Time Spent: 1h 10m (was: 1h)
> Chicago Taxi on Dataflow is failing
> ---
>
> Key: BEAM-8114
> URL: https://issues.apache.org/jira/browse/BEAM-8114
> Project: Beam
> Issue Type: Bug
> Components: testing
>Reporter: Kamil Wasilewski
>Assignee: Michal Walenia
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> An exception is being raised when publishing metrics:
>
> {code:java}
> 16:48:57 value = self._prepare_runtime_metrics(runtime_list)
> 16:48:57 File
> "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python_Chicago_Taxi_Dataflow/src/sdks/python/apache_beam/testing/load_tests/load_test_metrics_utils.py",
> line 317, in _prepare_runtime_metrics
> 16:48:57 min_value = min(min_values)
> 16:48:57 ValueError: min() arg is an empty sequence
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work logged] (BEAM-8114) Chicago Taxi on Dataflow is failing
[
https://issues.apache.org/jira/browse/BEAM-8114?focusedWorklogId=305074&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305074
]
ASF GitHub Bot logged work on BEAM-8114:
Author: ASF GitHub Bot
Created on: 02/Sep/19 07:05
Start Date: 02/Sep/19 07:05
Worklog Time Spent: 10m
Work Description: mwalenia commented on issue #9456: [BEAM-8114] Fix
failing Chicago Taxi Example job on Jenkins
URL: https://github.com/apache/beam/pull/9456#issuecomment-527028656
Run Chicago Taxi on Dataflow
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 305074)
Time Spent: 1h (was: 50m)
> Chicago Taxi on Dataflow is failing
> ---
>
> Key: BEAM-8114
> URL: https://issues.apache.org/jira/browse/BEAM-8114
> Project: Beam
> Issue Type: Bug
> Components: testing
>Reporter: Kamil Wasilewski
>Assignee: Michal Walenia
>Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> An exception is being raised when publishing metrics:
>
> {code:java}
> 16:48:57 value = self._prepare_runtime_metrics(runtime_list)
> 16:48:57 File
> "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python_Chicago_Taxi_Dataflow/src/sdks/python/apache_beam/testing/load_tests/load_test_metrics_utils.py",
> line 317, in _prepare_runtime_metrics
> 16:48:57 min_value = min(min_values)
> 16:48:57 ValueError: min() arg is an empty sequence
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
