flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] dawidwys opened a new pull request #7324: Cep iterative condition timer service
Date Tue, 18 Dec 2018 10:24:01 GMT
dawidwys opened a new pull request #7324: Cep iterative condition timer service
URL: https://github.com/apache/flink/pull/7324
 
 
   ## What is the purpose of the change
   
   This is a follow-up PR to #7280 that gives similar access to `TimerContext` in `IterativeCondition`
   
   ## Brief change log
   
     - 570b7ea - b73fa5e - this is covered in #7280
     - 86b3673 - refactors how we create nfa test harness, so that it is easier to plug in
service (e.g `CepTimerService`) implementations.
     - b079127 Adds `CepTimerService` abstraction that gives `NFA` access to time related
characteristics. It is passed from `CepOperator` to `NFA` then it is used while evaluation
`IterativeCondition` to implement `TimerContext` methods.
   
   
   ## Verifying this change
   
   - Added tests in `org.apache.flink.cep.nfa.NFAIterativeConditionTimerContextTest`
   
   ## 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)
   

----------------------------------------------------------------
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