Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,8 @@ public PCollection<BeamRecord> buildBeamPipeline(PCollectionTuple inputPCollecti
BeamSqlRelUtils.getBeamRelInput(input).buildBeamPipeline(inputPCollections, sqlEnv);
if (windowFieldIdx != -1) {
upstream = upstream.apply(stageName + "assignEventTimestamp", WithTimestamps
.of(new BeamAggregationTransforms.WindowTimestampFn(windowFieldIdx)))
.of(new BeamAggregationTransforms.WindowTimestampFn(windowFieldIdx))
.withAllowedTimestampSkew(new Duration(Long.MAX_VALUE)))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two comments here:

  • Will other DoFns we defined in BeamSQL have the similar issue? (The classes in org.apache.beam.sdk.extensions.sql.impl.transform package)
  • In the future, the allowed timestamp skew might be better passed in as a config to the BeamSql api?(I am ok to keep it hardcoded in this PR.)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This is the only place where we assign EventTimestamp explicitly;
  2. We may not need this parameter, now the optional aligned time in tumble, hop and session is used as max_deplay_time;

.setCoder(upstream.getCoder());
}

Expand Down