Skip to content

[BEAM-3161] Cannot output with timestamp XXXX#4101

Closed
mingmxu wants to merge 1 commit intoapache:masterfrom
mingmxu:BEAM-3161
Closed

[BEAM-3161] Cannot output with timestamp XXXX#4101
mingmxu wants to merge 1 commit intoapache:masterfrom
mingmxu:BEAM-3161

Conversation

@mingmxu
Copy link

@mingmxu mingmxu commented Nov 8, 2017

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;

Copy link
Contributor

@xumingming xumingming left a comment

Choose a reason for hiding this comment

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

LGTM

@asfgit asfgit closed this in 4451d55 Nov 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants