flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] kl0u opened a new pull request #6871: [FLINK-10583][table] Add base TwoInputStreamOperator with TTL operator.
Date Wed, 17 Oct 2018 14:10:33 GMT
kl0u opened a new pull request #6871: [FLINK-10583][table] Add base TwoInputStreamOperator
with TTL operator.
URL: https://github.com/apache/flink/pull/6871
 
 
   ## What is the purpose of the change
   
   This is the first step for the implementation of FLINK-10583 and FLINK-10584.
   
   It introduces the `AbstractTwoInputStreamOperatorWithTTL` which contains the basic functionality
for implementing state TTL based on timers.
   
   This operator makes sure that:
   1) only at most one timer is registered per key
   2) both "sides" of the operator (processElement1 and processElement2) are treated equally
when it comes to registering cleanup timers.
   
   ## Verifying this change
   
   Added the `AbstractTwoInputStreamOperatorWithTTLTest` with tests for the class.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes
/ **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not
documented)
   
   R @pnowojski 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message