[jira] [Commented] (BEAM-9486) Python 2 PostCommit Failures due to time-out in 2.20.0 release branch

[Rui Wang (Jira)]

[ 
https://issues.apache.org/jira/browse/BEAM-9486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087370#comment-17087370
 ] 

Rui Wang commented on BEAM-9486:


cc [~ibzib] it might still exist in 2.21.0 release branch. 

The root cause is still unknown but it was not a 2.20.0 release blocker.

> Python 2 PostCommit Failures due to time-out in 2.20.0 release branch
> -
>
> Key: BEAM-9486
> URL: https://issues.apache.org/jira/browse/BEAM-9486
> Project: Beam
>  Issue Type: Bug
>  Components: test-failures
>Reporter: Rui Wang
>Assignee: Rui Wang
>Priority: Major
>
> https://builds.apache.org/job/beam_PostCommit_Python2_PR/195/
> https://builds.apache.org/job/beam_PostCommit_Python2_PR/196/
> https://builds.apache.org/job/beam_PostCommit_Python2_PR/198/
> They might be related to this error message:
> {code:java}
> 03:42:13 RuntimeError: BigQuery job 
> beam_load_2020_03_10_034115_50_bc104bcc3054360def24bf4ca8246e92_428184e062fc4771848d3c187f46f941
>  failed. Error Result:  03:42:13  message: u'No schema specified on job or table.'
> 03:42:13  reason: u'invalid'> [while running 
> 'WriteWithMultipleDests/BigQueryBatchFileLoads/WaitForTempTableLoadJobs/WaitForTempTableLoadJobs']
> 03:42:13 
> 03:42:18 
> INFO:apache_beam.runners.dataflow.dataflow_runner:2020-03-10T03:42:15.301Z: 
> JOB_MESSAGE_ERROR: Traceback (most recent call last):
> 03:42:18   File 
> "/usr/local/lib/python2.7/site-packages/dataflow_worker/batchworker.py", line 
> 647, in do_work
> 03:42:18 work_executor.execute()
> 03:42:18   File 
> "/usr/local/lib/python2.7/site-packages/dataflow_worker/executor.py", line 
> 176, in execute
> 03:42:18 op.start()
> 03:42:18   File "dataflow_worker/native_operations.py", line 38, in 
> dataflow_worker.native_operations.NativeReadOperation.start
> 03:42:18 def start(self):
> 03:42:18   File "dataflow_worker/native_operations.py", line 39, in 
> dataflow_worker.native_operations.NativeReadOperation.start
> 03:42:18 with self.scoped_start_state:
> 03:42:18   File "dataflow_worker/native_operations.py", line 44, in 
> dataflow_worker.native_operations.NativeReadOperation.start
> 03:42:18 with self.spec.source.reader() as reader:
> 03:42:18   File "dataflow_worker/native_operations.py", line 54, in 
> dataflow_worker.native_operations.NativeReadOperation.start
> 03:42:18 self.output(windowed_value)
> 03:42:18   File "apache_beam/runners/worker/operations.py", line 329, in 
> apache_beam.runners.worker.operations.Operation.output
> 03:42:18 cython.cast(Receiver, 
> self.receivers[output_index]).receive(windowed_value)
> 03:42:18   File "apache_beam/runners/worker/operations.py", line 135, in 
> apache_beam.runners.worker.operations.ConsumerSet.receive
> 03:42:18 cython.cast(Operation, consumer).process(windowed_value)
> 03:42:18   File "apache_beam/runners/worker/operations.py", line 682, in 
> apache_beam.runners.worker.operations.DoOperation.process
> 03:42:18 with self.scoped_process_state:
> 03:42:18   File "apache_beam/runners/worker/operations.py", line 683, in 
> apache_beam.runners.worker.operations.DoOperation.process
> 03:42:18 delayed_application = self.dofn_runner.process(o)
> 03:42:18   File "apache_beam/runners/common.py", line 952, in 
> apache_beam.runners.common.DoFnRunner.process
> 03:42:18 self._reraise_augmented(exn)
> 03:42:18   File "apache_beam/runners/common.py", line 1028, in 
> apache_beam.runners.common.DoFnRunner._reraise_augmented
> 03:42:18 raise_with_traceback(new_exn)
> 03:42:18   File "apache_beam/runners/common.py", line 950, in 
> apache_beam.runners.common.DoFnRunner.process
> 03:42:18 return self.do_fn_invoker.invoke_process(windowed_value)
> 03:42:18   File "apache_beam/runners/common.py", line 720, in 
> apache_beam.runners.common.PerWindowInvoker.invoke_process
> 03:42:18 self._invoke_process_per_window(
> 03:42:18   File "apache_beam/runners/common.py", line 803, in 
> apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window
> 03:42:18 self.process_method(*args_for_process),
> 03:42:18   File 
> "/usr/local/lib/python2.7/site-packages/apache_beam/io/gcp/bigquery_file_loads.py",
>  line 543, in process
> 03:42:18 self.bq_wrapper.wait_for_bq_job(ref, sleep_duration_sec=10, 
> max_retries=0)
> 03:42:18   File 
> "/usr/local/lib/python2.7/site-packages/apache_beam/io/gcp/bigquery_tools.py",
>  line 424, in wait_for_bq_job
> 03:42:18 job_reference.jobId, job.status.errorResult))
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (BEAM-9751) Upgrade ZetaSQL to 2020.04.1

[Rui Wang (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Wang resolved BEAM-9751.

Fix Version/s: Not applicable
   Resolution: Fixed

> Upgrade ZetaSQL to 2020.04.1
> 
>
> Key: BEAM-9751
> URL: https://issues.apache.org/jira/browse/BEAM-9751
> Project: Beam
>  Issue Type: Task
>  Components: dsl-sql-zetasql
>Reporter: Rui Wang
>Assignee: Rui Wang
>Priority: Major
> Fix For: Not applicable
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9770) Add BigQuery DeadLetter pattern to Patterns Page

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9770?focusedWorklogId=425171=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425171
 ]

ASF GitHub Bot logged work on BEAM-9770:


Author: ASF GitHub Bot
Created on: 20/Apr/20 01:06
Start Date: 20/Apr/20 01:06
Worklog Time Spent: 10m 
  Work Description: rezarokni commented on a change in pull request #11437:
URL: https://github.com/apache/beam/pull/11437#discussion_r411034442



##
File path: 
examples/java/src/main/java/org/apache/beam/examples/snippets/Snippets.java
##
@@ -753,35 +750,93 @@ public static void main(String[] args) {
   // [START CustomSessionWindow5]
 
   PCollection p =
-  Pipeline.create()
-  .apply(
-  "Create data",
-  Create.timestamped(
-  TimestampedValue.of(
-  new TableRow().set("user", "mobile").set("score", 
12).set("gap", 5),
-  new Instant()),
-  TimestampedValue.of(
-  new TableRow().set("user", "desktop").set("score", 
4), new Instant()),
-  TimestampedValue.of(
-  new TableRow().set("user", "mobile").set("score", 
-3).set("gap", 5),
-  new Instant().plus(2000)),
-  TimestampedValue.of(
-  new TableRow().set("user", "mobile").set("score", 
2).set("gap", 5),
-  new Instant().plus(9000)),
-  TimestampedValue.of(
-  new TableRow().set("user", "mobile").set("score", 
7).set("gap", 5),
-  new Instant().plus(12000)),
-  TimestampedValue.of(
-  new TableRow().set("user", "desktop").set("score", 
10),
-  new Instant().plus(12000;
+  Pipeline.create()
+  .apply(
+  "Create data",
+  Create.timestamped(
+  TimestampedValue.of(
+  new TableRow().set("user", 
"mobile").set("score", 12).set("gap", 5),
+  new Instant()),
+  TimestampedValue.of(
+  new TableRow().set("user", 
"desktop").set("score", 4), new Instant()),
+  TimestampedValue.of(
+  new TableRow().set("user", 
"mobile").set("score", -3).set("gap", 5),
+  new Instant().plus(2000)),
+  TimestampedValue.of(
+  new TableRow().set("user", 
"mobile").set("score", 2).set("gap", 5),
+  new Instant().plus(9000)),
+  TimestampedValue.of(
+  new TableRow().set("user", 
"mobile").set("score", 7).set("gap", 5),
+  new Instant().plus(12000)),
+  TimestampedValue.of(
+  new TableRow().set("user", 
"desktop").set("score", 10),
+  new Instant().plus(12000;
   // [END CustomSessionWindow5]
 
   // [START CustomSessionWindow6]
   p.apply(
-  "Window into sessions",
-  Window.into(
-  
DynamicSessions.withDefaultGapDuration(Duration.standardSeconds(10;
+  "Window into sessions",
+  Window.into(
+  
DynamicSessions.withDefaultGapDuration(Duration.standardSeconds(10;
   // [END CustomSessionWindow6]
+}
+
+public static class DeadLetterBigQuery {
+  public static void deadletter(String[] args) {
+// [START BigQueryIODeadLetter]
+// Create pipeline
+PipelineOptions options =
+
PipelineOptionsFactory.fromArgs(args).withValidation().as(BigQueryOptions.class);
+
+Pipeline p = Pipeline.create(options);
+
+// Create a bug by writing the 2nd value as null. The API will 
correctly
+// throw an error when trying to insert a null value into a REQUIRED 
field.
+WriteResult result =
+p.apply(Create.of(1, 2))
+.apply(
+BigQueryIO.write()
+.withSchema(
+new TableSchema()
+.setFields(
+

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425121=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425121
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 19:28
Start Date: 19/Apr/20 19:28
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616211669
 
 
   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: 425121)
Time Spent: 7h  (was: 6h 50m)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 7h
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425122=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425122
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 19:28
Start Date: 19/Apr/20 19:28
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616211695
 
 
   Run Flink Runner Nexmark Tests
 

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: 425122)
Time Spent: 7h 10m  (was: 7h)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 7h 10m
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425120=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425120
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 19:28
Start Date: 19/Apr/20 19:28
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616211644
 
 
   Run Java Flink PortableValidatesRunner Streaming
 

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: 425120)
Time Spent: 6h 50m  (was: 6h 40m)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 6h 50m
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425113=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425113
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 18:31
Start Date: 19/Apr/20 18:31
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616202575
 
 
   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: 425113)
Time Spent: 6.5h  (was: 6h 20m)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425114=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425114
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 18:31
Start Date: 19/Apr/20 18:31
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616202637
 
 
   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: 425114)
Time Spent: 6h 40m  (was: 6.5h)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 6h 40m
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425096=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425096
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 15:54
Start Date: 19/Apr/20 15:54
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616168344
 
 
   Run Flink Runner Nexmark Tests
 

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: 425096)
Time Spent: 6h 20m  (was: 6h 10m)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 6h 20m
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425095=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425095
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 15:54
Start Date: 19/Apr/20 15:54
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616168266
 
 
   Run Java Flink PortableValidatesRunner Streaming
 

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: 425095)
Time Spent: 6h 10m  (was: 6h)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9733) ImpulseSourceFunction does not emit a final watermark

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425094=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425094
 ]

ASF GitHub Bot logged work on BEAM-9733:


Author: ASF GitHub Bot
Created on: 19/Apr/20 15:53
Start Date: 19/Apr/20 15:53
Worklog Time Spent: 10m 
  Work Description: mxm commented on issue #11362: [BEAM-9733] Always let 
ImpulseSourceFunction emit a final watermark
URL: https://github.com/apache/beam/pull/11362#issuecomment-616168234
 
 
   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: 425094)
Time Spent: 6h  (was: 5h 50m)

> ImpulseSourceFunction does not emit a final watermark
> -
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
>  Issue Type: Bug
>  Components: runner-flink
>Reporter: Maximilian Michels
>Assignee: Maximilian Michels
>Priority: Critical
> Fix For: 2.21.0
>
>  Time Spent: 6h
>  Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark, 
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the 
> flag is used in tests to shutdown the pipeline after reading all data). Most 
> pipelines will be long-running and thus do not specify the flag. 
> Not sending out the final watermark causes GroupByKey to hold back the data 
> of event time windows until the pipeline is shut down (the final watermark is 
> always emitted on pipeline shutdown which is why using the above flag works).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9678) Introduction Kata | Go SDK Code Katas

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9678?focusedWorklogId=425073=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425073
 ]

ASF GitHub Bot logged work on BEAM-9678:


Author: ASF GitHub Bot
Created on: 19/Apr/20 13:42
Start Date: 19/Apr/20 13:42
Worklog Time Spent: 10m 
  Work Description: lostluck commented on issue #11340: [BEAM-9678] Create 
Go SDK introduction kata
URL: https://github.com/apache/beam/pull/11340#issuecomment-616137818
 
 
   As noted in a previous reply, i already submitted a change to ignore go.sum
   files. (It's ok, there were many replies).
   
   
https://github.com/apache/beam/blob/7869455ff38ce4791c5531022ffb75e7f007e06e/build.gradle#L77
   
   On Sun, Apr 19, 2020, 12:15 AM Henry Suryawirawan 
   wrote:
   
   > I'd suggest we do the same for the go.sum files.
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > , or
   > unsubscribe
   > 

   > .
   >
   
 

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: 425073)
Time Spent: 6h 40m  (was: 6.5h)

> Introduction Kata | Go SDK Code Katas
> -
>
> Key: BEAM-9678
> URL: https://issues.apache.org/jira/browse/BEAM-9678
> Project: Beam
>  Issue Type: Sub-task
>  Components: katas, sdk-go
>Reporter: Damon Douglas
>Assignee: Damon Douglas
>Priority: Major
> Fix For: Not applicable
>
>  Time Spent: 6h 40m
>  Remaining Estimate: 0h
>
> An Introduction kata patterns after 
> [https://github.com/apache/beam/tree/master/learning/katas/java/Introduction] 
> where the take away is an individual's ability to start an Apache Beam 
> pipeline using the Golang SDK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (BEAM-9717) python-future cause ImportError on Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata reassigned BEAM-9717:
---

Assignee: yoshiki obata

> python-future cause ImportError on Python 3.8
> -
>
> Key: BEAM-9717
> URL: https://issues.apache.org/jira/browse/BEAM-9717
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Assignee: yoshiki obata
>Priority: Major
>
> python-future 0.16.0 installed on apache-beam 2.19.0 cause ImportError when 
> used in Python 3.8 [1],  that makes many tests FAIL.
> This problem is already resolved in newer version, we must update it to the 
> latest.
> [1] https://github.com/PythonCharmers/python-future/issues/447



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (BEAM-9701) Enable installing on Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata reassigned BEAM-9701:
---

Assignee: yoshiki obata

> Enable installing on Python 3.8
> ---
>
> Key: BEAM-9701
> URL: https://issues.apache.org/jira/browse/BEAM-9701
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Assignee: yoshiki obata
>Priority: Major
>
> We cannot *pip install apache-beam* on Python 3.8 because building wheels of 
> fastavro -and pyarrow- are failed on it.
> Updating versions of them at setup.py and confirm there is no effect for 
> other Python versions to do so are needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (BEAM-9717) python-future cause ImportError on Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata updated BEAM-9717:

Status: Open  (was: Triage Needed)

> python-future cause ImportError on Python 3.8
> -
>
> Key: BEAM-9717
> URL: https://issues.apache.org/jira/browse/BEAM-9717
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Priority: Major
>
> python-future 0.16.0 installed on apache-beam 2.19.0 cause ImportError when 
> used in Python 3.8 [1],  that makes many tests FAIL.
> This problem is already resolved in newer version, we must update it to the 
> latest.
> [1] https://github.com/PythonCharmers/python-future/issues/447



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (BEAM-9701) Enable installing on Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata updated BEAM-9701:

Status: Open  (was: Triage Needed)

> Enable installing on Python 3.8
> ---
>
> Key: BEAM-9701
> URL: https://issues.apache.org/jira/browse/BEAM-9701
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Priority: Major
>
> We cannot *pip install apache-beam* on Python 3.8 because building wheels of 
> fastavro -and pyarrow- are failed on it.
> Updating versions of them at setup.py and confirm there is no effect for 
> other Python versions to do so are needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (BEAM-9755) infer_return_type does not infer as expected in Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata updated BEAM-9755:

Status: Open  (was: Triage Needed)

> infer_return_type does not infer as expected in Python 3.8
> --
>
> Key: BEAM-9755
> URL: https://issues.apache.org/jira/browse/BEAM-9755
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Assignee: yoshiki obata
>Priority: Major
>
> apache_beam.typehints.trivial_inference.infer_return_type does not return 
> type as expected in Python 3.8.
>  And this cause testDictComprehensionSimple 
> (apache_beam.typehints.trivial_inference_test.TrivialInferenceTest) FAIL.
>  - Python 3.7.7
> {code:python}
>  >> from apache_beam.typehints.trivial_inference import infer_return_type
>  >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
> depth=5)
>  Dict[str, int]{code}
>  - Python 3.8.2
> {code:python}
>  >> from apache_beam.typehints.trivial_inference import infer_return_type
>  >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
> depth=5)
>  Dict[int, str]{code}
>  
> CPython bytecode changes[1] may affect.
>  [1] https://docs.python.org/3/whatsnew/3.8.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (BEAM-9754) Dataflow runner currently does not support Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata updated BEAM-9754:

Status: Open  (was: Triage Needed)

> Dataflow runner currently does not support Python 3.8
> -
>
> Key: BEAM-9754
> URL: https://issues.apache.org/jira/browse/BEAM-9754
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Assignee: yoshiki obata
>Priority: Major
>
> Following tests fail due to the dataflow runner not supporting Python 3.8:
> - test_default_ip_configuration 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_experiment_use_multiple_sdk_containers 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_flexrs_blank 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_flexrs_cost 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_flexrs_speed 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_harness_override_absent_in_released_sdks_with_runner_v2 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_harness_override_absent_in_unreleased_sdk 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_harness_override_custom_in_released_sdks 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_harness_override_custom_in_released_sdks_with_runner_v2 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_harness_override_default_in_released_sdks 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_harness_override_uses_base_version_in_rc_releases 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_number_of_worker_harness_threads 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_pinned_worker_harness_image_tag_used_in_dev_sdk 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_pipeline_url 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_private_ip_configuration 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_public_ip_configuration 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_sdk_harness_container_images_get_set 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_set_network 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_set_subnetwork 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_worker_harness_image_tag_matches_base_sdk_version_of_an_rc 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_worker_harness_image_tag_matches_released_sdk_version 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_worker_harness_override_takes_precedence_over_sdk_defaults 
> (apache_beam.runners.dataflow.internal.apiclient_test.UtilTest)
> - test_biqquery_read_streaming_fail 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_dataflow_worker_jar_flag_adds_use_staged_worker_jar_experiment 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_dataflow_worker_jar_flag_non_fnapi_noop 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_min_cpu_platform_flag_is_propagated_to_experiments 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_remote_runner_display_data 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_remote_runner_translation 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_streaming_create_translation 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_streaming_engine_flag_adds_windmill_experiments 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_unsupported_fnapi_features 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_upload_graph_experiment 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_use_fastavro_experiment_is_added_on_py3_and_onwards 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_use_fastavro_experiment_is_not_added_when_use_avro_is_present 
> (apache_beam.runners.dataflow.dataflow_runner_test.DataflowRunnerTest)
> - test_bad_path 
> (apache_beam.runners.dataflow.template_runner_test.TemplatingDataflowRunnerTest)
> - test_full_completion 
> (apache_beam.runners.dataflow.template_runner_test.TemplatingDataflowRunnerTest)
> Sample error message:
> {code}
> ==
> ERROR: test_default_ip_configuration 

[jira] [Assigned] (BEAM-9755) infer_return_type does not infer as expected in Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata reassigned BEAM-9755:
---

Assignee: yoshiki obata

> infer_return_type does not infer as expected in Python 3.8
> --
>
> Key: BEAM-9755
> URL: https://issues.apache.org/jira/browse/BEAM-9755
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Assignee: yoshiki obata
>Priority: Major
>
> apache_beam.typehints.trivial_inference.infer_return_type does not return 
> type as expected in Python 3.8.
>  And this cause testDictComprehensionSimple 
> (apache_beam.typehints.trivial_inference_test.TrivialInferenceTest) FAIL.
>  - Python 3.7.7
> {code:python}
>  >> from apache_beam.typehints.trivial_inference import infer_return_type
>  >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
> depth=5)
>  Dict[str, int]{code}
>  - Python 3.8.2
> {code:python}
>  >> from apache_beam.typehints.trivial_inference import infer_return_type
>  >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
> depth=5)
>  Dict[int, str]{code}
>  
> CPython bytecode changes[1] may affect.
>  [1] https://docs.python.org/3/whatsnew/3.8.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (BEAM-9755) infer_return_type does not infer as expected in Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata updated BEAM-9755:

Description: 
apache_beam.typehints.trivial_inference.infer_return_type does not return type 
as expected in Python 3.8.
 And this cause testDictComprehensionSimple 
(apache_beam.typehints.trivial_inference_test.TrivialInferenceTest) FAIL.
 - Python 3.7.7
{code:python}
 >> from apache_beam.typehints.trivial_inference import infer_return_type
 >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
 >> depth=5)
 Dict[str, int]{code}

 - Python 3.8.2
{code:python}
 >> from apache_beam.typehints.trivial_inference import infer_return_type
 >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
 >> depth=5)
 Dict[int, str]{code}
 

CPython bytecode changes[1] may affect.

 [1] https://docs.python.org/3/whatsnew/3.8.html

  was:
apache_beam.typehints.trivial_inference.infer_return_type does not return type 
as expected in Python 3.8.
And this cause testDictComprehensionSimple 
(apache_beam.typehints.trivial_inference_test.TrivialInferenceTest) FAIL.

- Python 3.7.7
{code:Python}
 >> from apache_beam.typehints.trivial_inference import infer_return_type
 >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
 >> depth=5)
 Dict[str, int]{code}
- Python 3.8.2
{code:Python}
 >> from apache_beam.typehints.trivial_inference import infer_return_type
 >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
 >> depth=5)
 Dict[int, str]{code}
 


> infer_return_type does not infer as expected in Python 3.8
> --
>
> Key: BEAM-9755
> URL: https://issues.apache.org/jira/browse/BEAM-9755
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Priority: Major
>
> apache_beam.typehints.trivial_inference.infer_return_type does not return 
> type as expected in Python 3.8.
>  And this cause testDictComprehensionSimple 
> (apache_beam.typehints.trivial_inference_test.TrivialInferenceTest) FAIL.
>  - Python 3.7.7
> {code:python}
>  >> from apache_beam.typehints.trivial_inference import infer_return_type
>  >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
> depth=5)
>  Dict[str, int]{code}
>  - Python 3.8.2
> {code:python}
>  >> from apache_beam.typehints.trivial_inference import infer_return_type
>  >> infer_return_type(lambda _list: {'a': 1 for _ in _list}, [], debug=False, 
> depth=5)
>  Dict[int, str]{code}
>  
> CPython bytecode changes[1] may affect.
>  [1] https://docs.python.org/3/whatsnew/3.8.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (BEAM-9701) Enable installing on Python 3.8

[yoshiki obata (Jira)]

[ 
https://issues.apache.org/jira/browse/BEAM-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086939#comment-17086939
 ] 

yoshiki obata commented on BEAM-9701:
-

pyarrow dependent version is updated on 2.20.0, so we have to update fastavro's 
one.

> Enable installing on Python 3.8
> ---
>
> Key: BEAM-9701
> URL: https://issues.apache.org/jira/browse/BEAM-9701
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Priority: Major
>
> We cannot *pip install apache-beam* on Python 3.8 because building wheels of 
> fastavro -and pyarrow- are failed on it.
> Updating versions of them at setup.py and confirm there is no effect for 
> other Python versions to do so are needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (BEAM-9701) Enable installing on Python 3.8

[yoshiki obata (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

yoshiki obata updated BEAM-9701:

Description: 
We cannot *pip install apache-beam* on Python 3.8 because building wheels of 
fastavro -and pyarrow- are failed on it.
Updating versions of them at setup.py and confirm there is no effect for other 
Python versions to do so are needed.

  was:
We cannot `pip install apache-beam` on Python 3.8 because building wheels of 
fastavro and pyarrow are failed on it.
Updating versions of them at setup.py and confirm there is no effect for other 
Python versions to do so are needed.


> Enable installing on Python 3.8
> ---
>
> Key: BEAM-9701
> URL: https://issues.apache.org/jira/browse/BEAM-9701
> Project: Beam
>  Issue Type: Sub-task
>  Components: sdk-py-core
>Reporter: yoshiki obata
>Priority: Major
>
> We cannot *pip install apache-beam* on Python 3.8 because building wheels of 
> fastavro -and pyarrow- are failed on it.
> Updating versions of them at setup.py and confirm there is no effect for 
> other Python versions to do so are needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9678) Introduction Kata | Go SDK Code Katas

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9678?focusedWorklogId=425024=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425024
 ]

ASF GitHub Bot logged work on BEAM-9678:


Author: ASF GitHub Bot
Created on: 19/Apr/20 07:15
Start Date: 19/Apr/20 07:15
Worklog Time Spent: 10m 
  Work Description: henryken commented on issue #11340: [BEAM-9678] Create 
Go SDK introduction kata
URL: https://github.com/apache/beam/pull/11340#issuecomment-616063862
 
 
   I'd suggest we do the same for the go.sum files.
 

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: 425024)
Time Spent: 6.5h  (was: 6h 20m)

> Introduction Kata | Go SDK Code Katas
> -
>
> Key: BEAM-9678
> URL: https://issues.apache.org/jira/browse/BEAM-9678
> Project: Beam
>  Issue Type: Sub-task
>  Components: katas, sdk-go
>Reporter: Damon Douglas
>Assignee: Damon Douglas
>Priority: Major
> Fix For: Not applicable
>
>  Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> An Introduction kata patterns after 
> [https://github.com/apache/beam/tree/master/learning/katas/java/Introduction] 
> where the take away is an individual's ability to start an Apache Beam 
> pipeline using the Golang SDK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (BEAM-9678) Introduction Kata | Go SDK Code Katas

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/BEAM-9678?focusedWorklogId=425023=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425023
 ]

ASF GitHub Bot logged work on BEAM-9678:


Author: ASF GitHub Bot
Created on: 19/Apr/20 07:14
Start Date: 19/Apr/20 07:14
Worklog Time Spent: 10m 
  Work Description: henryken commented on issue #11340: [BEAM-9678] Create 
Go SDK introduction kata
URL: https://github.com/apache/beam/pull/11340#issuecomment-616063770
 
 
   Yeah the *-remote-info.yaml files are auto generated and they are 
overwritten after the course has been uploaded.
 

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: 425023)
Time Spent: 6h 20m  (was: 6h 10m)

> Introduction Kata | Go SDK Code Katas
> -
>
> Key: BEAM-9678
> URL: https://issues.apache.org/jira/browse/BEAM-9678
> Project: Beam
>  Issue Type: Sub-task
>  Components: katas, sdk-go
>Reporter: Damon Douglas
>Assignee: Damon Douglas
>Priority: Major
> Fix For: Not applicable
>
>  Time Spent: 6h 20m
>  Remaining Estimate: 0h
>
> An Introduction kata patterns after 
> [https://github.com/apache/beam/tree/master/learning/katas/java/Introduction] 
> where the take away is an individual's ability to start an Apache Beam 
> pipeline using the Golang SDK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)