Github user rmetzger commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1764#discussion_r56802763
  
    --- Diff: 
flink-streaming-java/src/main/java/org/apache/flink/streaming/api/functions/FixedAllowedLatenessWatermarkEmitter.java
 ---
    @@ -0,0 +1,84 @@
    +/*
    + * 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.flink.streaming.api.functions;
    +
    +import org.apache.flink.streaming.api.watermark.Watermark;
    +import org.apache.flink.streaming.api.windowing.time.Time;
    +
    +/**
    + * This is a {@link AssignerWithPeriodicWatermarks} used to emit 
Watermarks that lag behind the element with
    + * the maximum timestamp (in EVENT_TIME) seen so far by a fixed period of 
time. This will help reduce the number
    + * of elements dropped due to lateness, in the case where we know that 
elements arrive no later than a certain
    --- End diff --
    
    elements are not dropped


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to