You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following pipeline fails to print out all numbers 1 to 100 when run on DirectRunner in streaming mode.
This was identified implementing org.apache.beam.sdk.io.gcp.pubsublite.ReadWriteIT, which uses a workaround for the bug in either Create or DirectRunner:
private static final int COUNT = 100;
private static AtomicInteger CREATED_COUNT = new AtomicInteger();
public
static void run(Pipeline pipeline) {
PCollection<Integer> indexes = pipeline.apply( "createIndexes",
Create.of(IntStream.range(0, COUNT).boxed().collect(Collectors.toList())));
indexes.apply(
"createMessages",
MapElements.via(
new SimpleFunction<Integer, Integer>(
index ->
{
System.err.println("Created message index " + createdCount.incrementAndGet());
return index;
}) {}));
pipeline.run().waitUntilFinish(); // Never terminates
}
Imported from Jira BEAM-12867. Original Jira may contain additional context.
Reported by: dpcollins-google.
The text was updated successfully, but these errors were encountered:
@dpcollins-google per my prior comment, can you confirm with a PAssert whether there is a lack of data processing actually occurring? Or, you may take the position that all side effects of a DoFn should have occurred before the pipeline shuts down. All in all, I am not convinced this is P1 but it could be a real bug.
The following pipeline fails to print out all numbers 1 to 100 when run on DirectRunner in streaming mode.
This was identified implementing org.apache.beam.sdk.io.gcp.pubsublite.ReadWriteIT, which uses a workaround for the bug in either Create or DirectRunner:
Imported from Jira BEAM-12867. Original Jira may contain additional context.
Reported by: dpcollins-google.
The text was updated successfully, but these errors were encountered: