[jira] [Work logged] (BEAM-7948) Add time-based cache threshold support in the Java data service
[
https://issues.apache.org/jira/browse/BEAM-7948?focusedWorklogId=345107=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345107
]
ASF GitHub Bot logged work on BEAM-7948:
Author: ASF GitHub Bot
Created on: 18/Nov/19 07:58
Start Date: 18/Nov/19 07:58
Worklog Time Spent: 10m
Work Description: sunjincheng121 commented on pull request #9949:
[BEAM-7948] Add time-based cache threshold support in the Java data s…
URL: https://github.com/apache/beam/pull/9949#discussion_r347238459
##
File path:
sdks/java/fn-execution/src/test/java/org/apache/beam/sdk/fn/data/BeamFnDataTimeBasedBufferingOutboundObserverTest.java
##
@@ -0,0 +1,139 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.beam.sdk.fn.data;
+
+import static
org.apache.beam.sdk.fn.data.BeamFnDataSizeBasedBufferingOutboundObserverTest.messageWithData;
+import static org.apache.beam.sdk.util.WindowedValue.valueInGlobalWindow;
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.fail;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collection;
+import java.util.concurrent.CountDownLatch;
+import java.util.function.Consumer;
+import org.apache.beam.model.fnexecution.v1.BeamFnApi.Elements;
+import org.apache.beam.sdk.coders.ByteArrayCoder;
+import org.apache.beam.sdk.coders.Coder;
+import org.apache.beam.sdk.coders.LengthPrefixCoder;
+import org.apache.beam.sdk.fn.test.TestStreams;
+import org.apache.beam.sdk.options.ExperimentalOptions;
+import org.apache.beam.sdk.options.PipelineOptions;
+import org.apache.beam.sdk.options.PipelineOptionsFactory;
+import org.apache.beam.sdk.util.WindowedValue;
+import
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.collect.Iterables;
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.junit.runners.JUnit4;
+
+/** Tests for {@link BeamFnDataTimeBasedBufferingOutboundObserver}. */
+@RunWith(JUnit4.class)
+public class BeamFnDataTimeBasedBufferingOutboundObserverTest {
+ private static final LogicalEndpoint OUTPUT_LOCATION =
LogicalEndpoint.of("777L", "555L");
+ private static final Coder> CODER =
+
LengthPrefixCoder.of(WindowedValue.getValueOnlyCoder(ByteArrayCoder.of()));
+
+ @Test
+ public void testConfiguredTimeLimit() throws Exception {
+Collection values = new ArrayList<>();
+PipelineOptions options = PipelineOptionsFactory.create();
+options
+.as(ExperimentalOptions.class)
+.setExperiments(Arrays.asList("beam_fn_api_data_buffer_time_limit=1"));
+final CountDownLatch waitForFlush = new CountDownLatch(1);
+CloseableFnDataReceiver> consumer =
+BeamFnDataBufferingOutboundObserver.forLocation(
+options,
+OUTPUT_LOCATION,
+CODER,
+TestStreams.withOnNext(
+(Consumer)
+e -> {
+ values.add(e);
+ waitForFlush.countDown();
+})
+.build());
+
+// Test that it emits when time passed the time limit
+consumer.accept(valueInGlobalWindow(new byte[1]));
+waitForFlush.await(); // wait the flush thread to flush the buffer
+assertEquals(messageWithData(new byte[1]), Iterables.get(values, 0));
+ }
+
+ @Test
+ public void testConfiguredTimeLimitExceptionPropagation() throws Exception {
+PipelineOptions options = PipelineOptionsFactory.create();
+options
+.as(ExperimentalOptions.class)
+.setExperiments(Arrays.asList("beam_fn_api_data_buffer_time_limit=1"));
+BeamFnDataTimeBasedBufferingOutboundObserver>
consumer =
+(BeamFnDataTimeBasedBufferingOutboundObserver>)
+BeamFnDataBufferingOutboundObserver.forLocation(
+options,
+OUTPUT_LOCATION,
+CODER,
+TestStreams.withOnNext(
+(Consumer)
+e -> {
+ throw new RuntimeException("");
+})
+
[jira] [Work logged] (BEAM-7948) Add time-based cache threshold support in the Java data service
[
https://issues.apache.org/jira/browse/BEAM-7948?focusedWorklogId=345098=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345098
]
ASF GitHub Bot logged work on BEAM-7948:
Author: ASF GitHub Bot
Created on: 18/Nov/19 07:40
Start Date: 18/Nov/19 07:40
Worklog Time Spent: 10m
Work Description: sunjincheng121 commented on pull request #9949:
[BEAM-7948] Add time-based cache threshold support in the Java data s…
URL: https://github.com/apache/beam/pull/9949#discussion_r347233168
##
File path:
sdks/java/fn-execution/src/main/java/org/apache/beam/sdk/fn/data/BeamFnDataTimeBasedBufferingOutboundObserver.java
##
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.beam.sdk.fn.data;
+
+import java.io.IOException;
+import java.util.concurrent.CancellationException;
+import java.util.concurrent.ExecutionException;
+import java.util.concurrent.Executors;
+import java.util.concurrent.ScheduledFuture;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.atomic.AtomicReference;
+import org.apache.beam.model.fnexecution.v1.BeamFnApi;
+import org.apache.beam.sdk.coders.Coder;
+import org.apache.beam.vendor.grpc.v1p21p0.io.grpc.stub.StreamObserver;
+import
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.annotations.VisibleForTesting;
+import
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.ThreadFactoryBuilder;
+
+/**
+ * A buffering outbound {@link FnDataReceiver} with both size-based buffer and
time-based buffer
+ * enabled for the Beam Fn Data API.
+ */
+public class BeamFnDataTimeBasedBufferingOutboundObserver
+extends BeamFnDataSizeBasedBufferingOutboundObserver {
+
+ private final Object lock;
+ private final ScheduledFuture flushFuture;
+ @VisibleForTesting final AtomicReference flushException;
+
+ BeamFnDataTimeBasedBufferingOutboundObserver(
+ int sizeLimit,
+ long timeLimit,
+ LogicalEndpoint outputLocation,
+ Coder coder,
+ StreamObserver outboundObserver) {
+super(sizeLimit, outputLocation, coder, outboundObserver);
+this.lock = new Object();
+this.flushFuture =
+Executors.newSingleThreadScheduledExecutor(
+new ThreadFactoryBuilder()
+.setDaemon(true)
+.setNameFormat("DataBufferOutboundFlusher-thread")
+.build())
+.scheduleAtFixedRate(this::periodicFlush, timeLimit, timeLimit,
TimeUnit.MILLISECONDS);
+this.flushException = new AtomicReference<>(null);
+ }
+
+ @Override
+ public void close() throws Exception {
+checkFlushThreadException();
+synchronized (lock) {
+ flushFuture.cancel(true);
+ try {
+flushFuture.get();
+ } catch (CancellationException | ExecutionException |
InterruptedException exn) {
+// expected
+ }
+}
+super.close();
+ }
+
+ @Override
+ public void flush() throws IOException {
+synchronized (lock) {
+ super.flush();
+}
+ }
+
+ @Override
+ public void accept(T t) throws IOException {
+checkFlushThreadException();
+super.accept(t);
+ }
+
+ private void periodicFlush() {
Review comment:
It's not possible to use the flush method directly as it throws an
IOException. It's a good idea to use `flushFuture.isDone()` to check the status
of the flush thread. Will be Updated. :)
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: 345098)
Time Spent: 1h 40m (was: 1.5h)
> Add time-based cache threshold support in the Java data service
> ---
>
> Key: BEAM-7948
> URL: https://issues.apache.org/jira/browse/BEAM-7948
> Project: Beam
>
[jira] [Work logged] (BEAM-7948) Add time-based cache threshold support in the Java data service
[
https://issues.apache.org/jira/browse/BEAM-7948?focusedWorklogId=345097=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345097
]
ASF GitHub Bot logged work on BEAM-7948:
Author: ASF GitHub Bot
Created on: 18/Nov/19 07:39
Start Date: 18/Nov/19 07:39
Worklog Time Spent: 10m
Work Description: sunjincheng121 commented on pull request #9949:
[BEAM-7948] Add time-based cache threshold support in the Java data s…
URL: https://github.com/apache/beam/pull/9949#discussion_r347232921
##
File path:
sdks/java/fn-execution/src/main/java/org/apache/beam/sdk/fn/data/BeamFnDataTimeBasedBufferingOutboundObserver.java
##
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.beam.sdk.fn.data;
+
+import java.io.IOException;
+import java.util.concurrent.CancellationException;
+import java.util.concurrent.ExecutionException;
+import java.util.concurrent.Executors;
+import java.util.concurrent.ScheduledFuture;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.atomic.AtomicReference;
+import org.apache.beam.model.fnexecution.v1.BeamFnApi;
+import org.apache.beam.sdk.coders.Coder;
+import org.apache.beam.vendor.grpc.v1p21p0.io.grpc.stub.StreamObserver;
+import
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.annotations.VisibleForTesting;
+import
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.ThreadFactoryBuilder;
+
+/**
+ * A buffering outbound {@link FnDataReceiver} with both size-based buffer and
time-based buffer
+ * enabled for the Beam Fn Data API.
+ */
+public class BeamFnDataTimeBasedBufferingOutboundObserver
+extends BeamFnDataSizeBasedBufferingOutboundObserver {
+
+ private final Object lock;
+ private final ScheduledFuture flushFuture;
+ @VisibleForTesting final AtomicReference flushException;
+
+ BeamFnDataTimeBasedBufferingOutboundObserver(
+ int sizeLimit,
+ long timeLimit,
+ LogicalEndpoint outputLocation,
+ Coder coder,
+ StreamObserver outboundObserver) {
+super(sizeLimit, outputLocation, coder, outboundObserver);
+this.lock = new Object();
+this.flushFuture =
+Executors.newSingleThreadScheduledExecutor(
+new ThreadFactoryBuilder()
+.setDaemon(true)
+.setNameFormat("DataBufferOutboundFlusher-thread")
+.build())
+.scheduleAtFixedRate(this::periodicFlush, timeLimit, timeLimit,
TimeUnit.MILLISECONDS);
+this.flushException = new AtomicReference<>(null);
+ }
+
+ @Override
+ public void close() throws Exception {
+checkFlushThreadException();
+synchronized (lock) {
+ flushFuture.cancel(true);
Review comment:
This is done by holding the flush lock and so it's guaranteed that the flush
thread is not flush data. I have renamed the "lock" to "flushLock" to make it
more clear.
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: 345097)
Time Spent: 1.5h (was: 1h 20m)
> Add time-based cache threshold support in the Java data service
> ---
>
> Key: BEAM-7948
> URL: https://issues.apache.org/jira/browse/BEAM-7948
> Project: Beam
> Issue Type: Sub-task
> Components: java-fn-execution
>Reporter: sunjincheng
>Assignee: sunjincheng
>Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently only size-based cache threshold is supported in data service. It
> should also support the time-based cache threshold. This is very important,
> especially for streaming jobs which are sensitive to the delay.
--
This message was sent by Atlassian Jira
[jira] [Work logged] (BEAM-7951) Allow runner to configure customization WindowedValue coder such as ValueOnlyWindowedValueCoder
[ https://issues.apache.org/jira/browse/BEAM-7951?focusedWorklogId=345079=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345079 ] ASF GitHub Bot logged work on BEAM-7951: Author: ASF GitHub Bot Created on: 18/Nov/19 06:25 Start Date: 18/Nov/19 06:25 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #9979: [BEAM-7951] Allow runner to configure customization WindowedValue coder. URL: https://github.com/apache/beam/pull/9979#issuecomment-554871240 Run Python PreCommit 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: 345079) Time Spent: 2h (was: 1h 50m) > Allow runner to configure customization WindowedValue coder such as > ValueOnlyWindowedValueCoder > --- > > Key: BEAM-7951 > URL: https://issues.apache.org/jira/browse/BEAM-7951 > Project: Beam > Issue Type: Sub-task > Components: java-fn-execution >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > The coder of WindowedValue cannot be configured and it’s always > FullWindowedValueCoder. We don't need to serialize the timestamp, window and > pane properties in Flink and so it will be better to make the coder > configurable (i.e. allowing to use ValueOnlyWindowedValueCoder) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-7951) Allow runner to configure customization WindowedValue coder such as ValueOnlyWindowedValueCoder
[ https://issues.apache.org/jira/browse/BEAM-7951?focusedWorklogId=345056=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345056 ] ASF GitHub Bot logged work on BEAM-7951: Author: ASF GitHub Bot Created on: 18/Nov/19 03:25 Start Date: 18/Nov/19 03:25 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #9979: [BEAM-7951] Allow runner to configure customization WindowedValue coder. URL: https://github.com/apache/beam/pull/9979#issuecomment-554834870 Run Java PreCommit 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: 345056) Time Spent: 1h 50m (was: 1h 40m) > Allow runner to configure customization WindowedValue coder such as > ValueOnlyWindowedValueCoder > --- > > Key: BEAM-7951 > URL: https://issues.apache.org/jira/browse/BEAM-7951 > Project: Beam > Issue Type: Sub-task > Components: java-fn-execution >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > The coder of WindowedValue cannot be configured and it’s always > FullWindowedValueCoder. We don't need to serialize the timestamp, window and > pane properties in Flink and so it will be better to make the coder > configurable (i.e. allowing to use ValueOnlyWindowedValueCoder) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-7951) Allow runner to configure customization WindowedValue coder such as ValueOnlyWindowedValueCoder
[ https://issues.apache.org/jira/browse/BEAM-7951?focusedWorklogId=345048=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345048 ] ASF GitHub Bot logged work on BEAM-7951: Author: ASF GitHub Bot Created on: 18/Nov/19 02:08 Start Date: 18/Nov/19 02:08 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #9979: [BEAM-7951] Allow runner to configure customization WindowedValue coder. URL: https://github.com/apache/beam/pull/9979#issuecomment-554820488 Run Portable_Python PreCommit 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: 345048) Time Spent: 1h 40m (was: 1.5h) > Allow runner to configure customization WindowedValue coder such as > ValueOnlyWindowedValueCoder > --- > > Key: BEAM-7951 > URL: https://issues.apache.org/jira/browse/BEAM-7951 > Project: Beam > Issue Type: Sub-task > Components: java-fn-execution >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > The coder of WindowedValue cannot be configured and it’s always > FullWindowedValueCoder. We don't need to serialize the timestamp, window and > pane properties in Flink and so it will be better to make the coder > configurable (i.e. allowing to use ValueOnlyWindowedValueCoder) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-8442) Unify bundle register in Python SDK harness
[ https://issues.apache.org/jira/browse/BEAM-8442?focusedWorklogId=345047=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345047 ] ASF GitHub Bot logged work on BEAM-8442: Author: ASF GitHub Bot Created on: 18/Nov/19 02:07 Start Date: 18/Nov/19 02:07 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #10004: [BEAM-8442] Unify bundle register in Python SDK harness URL: https://github.com/apache/beam/pull/10004#issuecomment-554820392 Hi @chamikaramj, I have create a JIRA. [BEAM-8733](https://issues.apache.org/jira/browse/BEAM-8733) to trace the discussion of this issue. I think it's better to continue the discussion in the JIRA. Feel free to correct me if this not make sense to you :) 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: 345047) Time Spent: 6h 20m (was: 6h 10m) > Unify bundle register in Python SDK harness > --- > > Key: BEAM-8442 > URL: https://issues.apache.org/jira/browse/BEAM-8442 > Project: Beam > Issue Type: Sub-task > Components: sdk-py-harness >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Fix For: 2.18.0 > > Time Spent: 6h 20m > Remaining Estimate: 0h > > There are two methods for bundle register in Python SDK harness: > `SdkHarness._request_register` and `SdkWorker.register.` It should be unfied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BEAM-8733) The "KeyError: u'-47'" error from line 305 of sdk_worker.py
[
https://issues.apache.org/jira/browse/BEAM-8733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976225#comment-16976225
]
sunjincheng commented on BEAM-8733:
---
Hi, Thanks for the log info, [~chamikara].
>From the exception log(the line number of RegisterAndProcessBundleOperation),
>it seems that the
>[commit|https://github.com/apache/beam/commit/686833381ecc92f0fbe04e576a582a7640ca7bbd]
> is not included in the DataFlow runner. Could you help to check this as this
>commit ensures that registration is executed successfully before executing
>process bundle request?
> The "KeyError: u'-47'" error from line 305 of sdk_worker.py
> ---
>
> Key: BEAM-8733
> URL: https://issues.apache.org/jira/browse/BEAM-8733
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
>Reporter: sunjincheng
>Priority: Major
> Fix For: 2.18.0
>
>
> The issue reported by [~chamikara], error message as follows:
> apache_beam/runners/worker/sdk_worker.py", line 305, in get
> self.fns[bundle_descriptor_id],
> KeyError: u'-47'
> {code}
> at
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
> at org.apache.beam.sdk.util.MoreFutures.get(MoreFutures.java:57)
> at
> org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.finish(RegisterAndProcessBundleOperation.java:330)
> at
> org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:85)
> at
> org.apache.beam.runners.dataflow.worker.fn.control.BeamFnMapTaskExecutor.execute(BeamFnMapTaskExecutor.java:125)
> at
> org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.executeWork(BatchDataflowWorker.java:411)
> at
> org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.doWork(BatchDataflowWorker.java:380)
> at
> org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.getAndPerformWork(BatchDataflowWorker.java:305)
> at
> org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.start(DataflowRunnerHarness.java:195)
> at
> org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.main(DataflowRunnerHarness.java:123)
> Suppressed: java.lang.IllegalStateException: Already closed.
> at
> org.apache.beam.sdk.fn.data.BeamFnDataBufferingOutboundObserver.close(BeamFnDataBufferingOutboundObserver.java:93)
> at
> org.apache.beam.runners.dataflow.worker.fn.data.RemoteGrpcPortWriteOperation.abort(RemoteGrpcPortWriteOperation.java:220)
> at
> org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:91)
> {code}
> More discussion info can be found here:
> https://github.com/apache/beam/pull/10004
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (BEAM-8733) The "KeyError: u'-47'" error from line 305 of sdk_worker.py
[
https://issues.apache.org/jira/browse/BEAM-8733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sunjincheng updated BEAM-8733:
--
Description:
The issue reported by [~chamikara], error message as follows:
apache_beam/runners/worker/sdk_worker.py", line 305, in get
self.fns[bundle_descriptor_id],
KeyError: u'-47'
{code}
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
at org.apache.beam.sdk.util.MoreFutures.get(MoreFutures.java:57)
at
org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.finish(RegisterAndProcessBundleOperation.java:330)
at
org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:85)
at
org.apache.beam.runners.dataflow.worker.fn.control.BeamFnMapTaskExecutor.execute(BeamFnMapTaskExecutor.java:125)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.executeWork(BatchDataflowWorker.java:411)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.doWork(BatchDataflowWorker.java:380)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.getAndPerformWork(BatchDataflowWorker.java:305)
at
org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.start(DataflowRunnerHarness.java:195)
at
org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.main(DataflowRunnerHarness.java:123)
Suppressed: java.lang.IllegalStateException: Already closed.
at
org.apache.beam.sdk.fn.data.BeamFnDataBufferingOutboundObserver.close(BeamFnDataBufferingOutboundObserver.java:93)
at
org.apache.beam.runners.dataflow.worker.fn.data.RemoteGrpcPortWriteOperation.abort(RemoteGrpcPortWriteOperation.java:220)
at
org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:91)
{code}
More discussion info can be found here:
https://github.com/apache/beam/pull/10004
was:
The issue reported by [~chamikara], error message as follows:
apache_beam/runners/worker/sdk_worker.py", line 305, in get
self.fns[bundle_descriptor_id],
KeyError: u'-47'
{code}
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
at org.apache.beam.sdk.util.MoreFutures.get(MoreFutures.java:57)
at
org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.finish(RegisterAndProcessBundleOperation.java:330)
at
org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:85)
at
org.apache.beam.runners.dataflow.worker.fn.control.BeamFnMapTaskExecutor.execute(BeamFnMapTaskExecutor.java:125)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.executeWork(BatchDataflowWorker.java:411)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.doWork(BatchDataflowWorker.java:380)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.getAndPerformWork(BatchDataflowWorker.java:305)
at
org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.start(DataflowRunnerHarness.java:195)
at
org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.main(DataflowRunnerHarness.java:123)
Suppressed: java.lang.IllegalStateException: Already closed.
at
org.apache.beam.sdk.fn.data.BeamFnDataBufferingOutboundObserver.close(BeamFnDataBufferingOutboundObserver.java:93)
at
org.apache.beam.runners.dataflow.worker.fn.data.RemoteGrpcPortWriteOperation.abort(RemoteGrpcPortWriteOperation.java:220)
at
org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:91)
{code}
> The "KeyError: u'-47'" error from line 305 of sdk_worker.py
> ---
>
> Key: BEAM-8733
> URL: https://issues.apache.org/jira/browse/BEAM-8733
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
>Reporter: sunjincheng
>Priority: Major
> Fix For: 2.18.0
>
>
> The issue reported by [~chamikara], error message as follows:
> apache_beam/runners/worker/sdk_worker.py", line 305, in get
> self.fns[bundle_descriptor_id],
> KeyError: u'-47'
> {code}
> at
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
> at org.apache.beam.sdk.util.MoreFutures.get(MoreFutures.java:57)
> at
> org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.finish(RegisterAndProcessBundleOperation.java:330)
> at
> org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:85)
> at
>
[jira] [Created] (BEAM-8733) The "KeyError: u'-47'" error from line 305 of sdk_worker.py
sunjincheng created BEAM-8733:
-
Summary: The "KeyError: u'-47'" error from line 305 of
sdk_worker.py
Key: BEAM-8733
URL: https://issues.apache.org/jira/browse/BEAM-8733
Project: Beam
Issue Type: Bug
Components: sdk-py-harness
Reporter: sunjincheng
Fix For: 2.18.0
The issue reported by [~chamikara], error message as follows:
apache_beam/runners/worker/sdk_worker.py", line 305, in get
self.fns[bundle_descriptor_id],
KeyError: u'-47'
{code}
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
at org.apache.beam.sdk.util.MoreFutures.get(MoreFutures.java:57)
at
org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.finish(RegisterAndProcessBundleOperation.java:330)
at
org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:85)
at
org.apache.beam.runners.dataflow.worker.fn.control.BeamFnMapTaskExecutor.execute(BeamFnMapTaskExecutor.java:125)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.executeWork(BatchDataflowWorker.java:411)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.doWork(BatchDataflowWorker.java:380)
at
org.apache.beam.runners.dataflow.worker.BatchDataflowWorker.getAndPerformWork(BatchDataflowWorker.java:305)
at
org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.start(DataflowRunnerHarness.java:195)
at
org.apache.beam.runners.dataflow.worker.DataflowRunnerHarness.main(DataflowRunnerHarness.java:123)
Suppressed: java.lang.IllegalStateException: Already closed.
at
org.apache.beam.sdk.fn.data.BeamFnDataBufferingOutboundObserver.close(BeamFnDataBufferingOutboundObserver.java:93)
at
org.apache.beam.runners.dataflow.worker.fn.data.RemoteGrpcPortWriteOperation.abort(RemoteGrpcPortWriteOperation.java:220)
at
org.apache.beam.runners.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:91)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (BEAM-7951) Allow runner to configure customization WindowedValue coder such as ValueOnlyWindowedValueCoder
[ https://issues.apache.org/jira/browse/BEAM-7951?focusedWorklogId=345040=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345040 ] ASF GitHub Bot logged work on BEAM-7951: Author: ASF GitHub Bot Created on: 18/Nov/19 01:41 Start Date: 18/Nov/19 01:41 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #9979: [BEAM-7951] Allow runner to configure customization WindowedValue coder. URL: https://github.com/apache/beam/pull/9979#issuecomment-554815776 Hi @mxm, Thanks a lot for your attention! I have updated the PR! :) The changes mainly include: 1. Add a ParameterizedWindowedValueCoder that with constant timestamp, windows and paneInfo. The ParameterizedWindowedValueCoder at the harness side init the constants from the payload of the coder, and to achieve this, the `message WindowInfo` is added in `beam_runner_api.proto` to carry the constant information. 2. Add WireCoderSetting in ExecutableStagePayload. With the WireCoderSetting, we can configure wire coder to `ParameterizedWindowedValueCoder` to avoid redundant encoding and decoding. Would be great if you can take a look! Best, 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: 345040) Time Spent: 1.5h (was: 1h 20m) > Allow runner to configure customization WindowedValue coder such as > ValueOnlyWindowedValueCoder > --- > > Key: BEAM-7951 > URL: https://issues.apache.org/jira/browse/BEAM-7951 > Project: Beam > Issue Type: Sub-task > Components: java-fn-execution >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > The coder of WindowedValue cannot be configured and it’s always > FullWindowedValueCoder. We don't need to serialize the timestamp, window and > pane properties in Flink and so it will be better to make the coder > configurable (i.e. allowing to use ValueOnlyWindowedValueCoder) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-7951) Allow runner to configure customization WindowedValue coder such as ValueOnlyWindowedValueCoder
[ https://issues.apache.org/jira/browse/BEAM-7951?focusedWorklogId=345039=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345039 ] ASF GitHub Bot logged work on BEAM-7951: Author: ASF GitHub Bot Created on: 18/Nov/19 01:41 Start Date: 18/Nov/19 01:41 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #9979: [BEAM-7951] Allow runner to configure customization WindowedValue coder. URL: https://github.com/apache/beam/pull/9979#issuecomment-554815776 Hi @mxm, Thanks a lot for your attention! I have updated the PR. The changes mainly include: 1. Add a ParameterizedWindowedValueCoder that with constant timestamp, windows and paneInfo. The ParameterizedWindowedValueCoder at the harness side init the constants from the payload of the coder, and to achieve this, the `message WindowInfo` is added in `beam_runner_api.proto` to carry the constant information. 2. Add WireCoderSetting in ExecutableStagePayload. With the WireCoderSetting, we can configure wire coder to `ParameterizedWindowedValueCoder` to avoid redundant encoding and decoding. Would be great if you can take a look! Best, 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: 345039) Time Spent: 1h 20m (was: 1h 10m) > Allow runner to configure customization WindowedValue coder such as > ValueOnlyWindowedValueCoder > --- > > Key: BEAM-7951 > URL: https://issues.apache.org/jira/browse/BEAM-7951 > Project: Beam > Issue Type: Sub-task > Components: java-fn-execution >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > The coder of WindowedValue cannot be configured and it’s always > FullWindowedValueCoder. We don't need to serialize the timestamp, window and > pane properties in Flink and so it will be better to make the coder > configurable (i.e. allowing to use ValueOnlyWindowedValueCoder) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-5440) Add option to mount a directory inside SDK harness containers
[
https://issues.apache.org/jira/browse/BEAM-5440?focusedWorklogId=345030=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345030
]
ASF GitHub Bot logged work on BEAM-5440:
Author: ASF GitHub Bot
Created on: 17/Nov/19 23:53
Start Date: 17/Nov/19 23:53
Worklog Time Spent: 10m
Work Description: stale[bot] commented on issue #8982: [BEAM-5440] Pass
docker run options to SDK harness containers
URL: https://github.com/apache/beam/pull/8982#issuecomment-554802377
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: 345030)
Time Spent: 3.5h (was: 3h 20m)
> Add option to mount a directory inside SDK harness containers
> -
>
> Key: BEAM-5440
> URL: https://issues.apache.org/jira/browse/BEAM-5440
> Project: Beam
> Issue Type: New Feature
> Components: java-fn-execution, sdk-java-core
>Reporter: Maximilian Michels
>Priority: Major
> Labels: portability, portability-flink
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> While experimenting with the Python SDK locally, I found it inconvenient that
> I can't mount a host directory to the Docker containers, i.e. the input must
> already be in the container and the results of a Write remain inside the
> container. For local testing, users may want to mount a host directory.
> Since BEAM-5288 the {{Environment}} carries explicit environment information,
> we could a) add volume args to the {{DockerPayload}}, or b) provide a general
> Docker arguments field.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (BEAM-8442) Unify bundle register in Python SDK harness
[ https://issues.apache.org/jira/browse/BEAM-8442?focusedWorklogId=345029=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345029 ] ASF GitHub Bot logged work on BEAM-8442: Author: ASF GitHub Bot Created on: 17/Nov/19 23:36 Start Date: 17/Nov/19 23:36 Worklog Time Spent: 10m Work Description: sunjincheng121 commented on issue #10004: [BEAM-8442] Unify bundle register in Python SDK harness URL: https://github.com/apache/beam/pull/10004#issuecomment-554800959 Hi, Thanks for the log info, @chamikaramj ! From the exception log(the line number of RegisterAndProcessBundleOperation), it seems that the [commit](https://github.com/apache/beam/commit/686833381ecc92f0fbe04e576a582a7640ca7bbd) is not included in the DataFlow runner. Could you help to check this as this commit ensures that registration is executed successfully before executing process bundle request? 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: 345029) Time Spent: 6h 10m (was: 6h) > Unify bundle register in Python SDK harness > --- > > Key: BEAM-8442 > URL: https://issues.apache.org/jira/browse/BEAM-8442 > Project: Beam > Issue Type: Sub-task > Components: sdk-py-harness >Reporter: sunjincheng >Assignee: sunjincheng >Priority: Major > Fix For: 2.18.0 > > Time Spent: 6h 10m > Remaining Estimate: 0h > > There are two methods for bundle register in Python SDK harness: > `SdkHarness._request_register` and `SdkWorker.register.` It should be unfied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (BEAM-3200) Streaming Pipeline throws RuntimeException when using DynamicDestinations and Method.FILE_LOADS
[
https://issues.apache.org/jira/browse/BEAM-3200?focusedWorklogId=345021=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345021
]
ASF GitHub Bot logged work on BEAM-3200:
Author: ASF GitHub Bot
Created on: 17/Nov/19 21:53
Start Date: 17/Nov/19 21:53
Worklog Time Spent: 10m
Work Description: stale[bot] commented on issue #9556: [BEAM-3200,
BEAM-3772] Fix: Honor create and write disposition with dynamic destinations
URL: https://github.com/apache/beam/pull/9556#issuecomment-554791525
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: 345021)
Time Spent: 6.5h (was: 6h 20m)
> Streaming Pipeline throws RuntimeException when using DynamicDestinations and
> Method.FILE_LOADS
> ---
>
> Key: BEAM-3200
> URL: https://issues.apache.org/jira/browse/BEAM-3200
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
>Affects Versions: 2.2.0
>Reporter: AJ
>Priority: Critical
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> I am trying to use Method.FILE_LOADS for loading data into BQ in my streaming
> pipeline using RC3 release of 2.2.0. I am writing to around 500 tables using
> DynamicDestinations and I am also using
> withCreateDisposition(CreateDisposition.CREATE_IF_NEEDED). Everything works
> fine when the first time bigquery load jobs get triggered. But on subsequent
> triggers pipeline throws a RuntimeException about table not found even though
> I created the pipeline with CreateDisposition.CREATE_IF_NEEDED. The exact
> exception is:
> {code}
> java.lang.RuntimeException: Failed to create load job with id prefix
> 717aed9ed1ef4aa7a616e1132f8b7f6d_a0928cae3d670b32f01ab2d9fe5cc0ee_1_1,
> reached max retries: 3, last failed load job: {
> "configuration" : {
> "load" : {
> "createDisposition" : "CREATE_NEVER",
> "destinationTable" : {
> "datasetId" : ...,
> "projectId" : ...,
> "tableId" :
> },
> "errors" : [ }
> "message" : "Not found: Table ,
> "reason" : "notFound"
> } ],
> {code}
> My theory is all the subsequent load jobs get trigged using CREATE_NEVER
> disposition and
> this might be due to
> https://github.com/apache/beam/blob/release-2.2.0/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/WriteTables.java#L140
> When using DynamicDestinations all the destination tables might not be known
> during the first trigger and hence the pipeline's create disposition should
> be respected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (BEAM-7629) Improve DoFn method validation in core/graph/fn.go
[ https://issues.apache.org/jira/browse/BEAM-7629?focusedWorklogId=345020=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345020 ] ASF GitHub Bot logged work on BEAM-7629: Author: ASF GitHub Bot Created on: 17/Nov/19 21:53 Start Date: 17/Nov/19 21:53 Worklog Time Spent: 10m Work Description: stale[bot] commented on issue #9609: [BEAM-7629] Go SDK: Refactoring fn order validation (INCOMPLETE) URL: https://github.com/apache/beam/pull/9609#issuecomment-554791523 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: 345020) Time Spent: 1h 50m (was: 1h 40m) > Improve DoFn method validation in core/graph/fn.go > -- > > Key: BEAM-7629 > URL: https://issues.apache.org/jira/browse/BEAM-7629 > Project: Beam > Issue Type: Improvement > Components: sdk-go >Reporter: Daniel Oliveira >Assignee: Daniel Oliveira >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Various improvements can be made to validating the signatures and type usages > in DoFns. Some things that should probably be checked: > * Check that StartBundle and FinishBundle contain any emit parameters and > side inputs present in ProcessElement > * Check that any side inputs/emits have correctly matching types between > Start/FinishBundle and ProcessElement > * Check that parameters and return values for the various methods are valid > (for ex. Teardown/Setup should have no params) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BEAM-7886) Make row coder a standard coder and implement in python
[ https://issues.apache.org/jira/browse/BEAM-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976165#comment-16976165 ] Chad Dombrova commented on BEAM-7886: - Is there a Jira for adding support for logical types? Is the idea with logical types that we would defer to the stock set of python coders for types outside of the native atomic types? e.g. timestamp, pickle, etc. > Make row coder a standard coder and implement in python > --- > > Key: BEAM-7886 > URL: https://issues.apache.org/jira/browse/BEAM-7886 > Project: Beam > Issue Type: Improvement > Components: beam-model, sdk-java-core, sdk-py-core >Reporter: Brian Hulette >Assignee: Brian Hulette >Priority: Major > Time Spent: 16h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (BEAM-7291) Upgrade hadoop-common
[ https://issues.apache.org/jira/browse/BEAM-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujuzi Moses reassigned BEAM-7291: -- Assignee: (was: Mujuzi Moses) > Upgrade hadoop-common > - > > Key: BEAM-7291 > URL: https://issues.apache.org/jira/browse/BEAM-7291 > Project: Beam > Issue Type: Sub-task > Components: dependencies >Reporter: Etienne Chauchot >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (BEAM-7291) Upgrade hadoop-common
[ https://issues.apache.org/jira/browse/BEAM-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujuzi Moses reassigned BEAM-7291: -- Assignee: Mujuzi Moses > Upgrade hadoop-common > - > > Key: BEAM-7291 > URL: https://issues.apache.org/jira/browse/BEAM-7291 > Project: Beam > Issue Type: Sub-task > Components: dependencies >Reporter: Etienne Chauchot >Assignee: Mujuzi Moses >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
