klion26 opened a new pull request #7921: [FLINK-11825][StateBackends] Resolve 
name class of StateTTL TimeCharacteristic class
URL: https://github.com/apache/flink/pull/7921
 
 
   ## What is the purpose of the change
   
   Resolve name class of StateTTL TimeCharacteristic class for at least 
following two reasons:
   1. Users get confused because the mistakenly import 
org.apache.flink.api.common.state.TimeCharacteristic.
   2. When using the StateTTL feature, users need to spell out the package name 
for org.apache.flink.api.common.state.TimeCharacteristic because the other 
class is most likely already imported.
   
   ## Brief change log
   
   Changes include:
   - Deprecated the StateTtlConfig#TimeCharacteristic class (for 
backward-compatibility).
   - Introduce a new class named StateTtlConfig#TtlTimeCharacteristic.
   
   We can not remove the class StateTtlConfig#TimeCharacteristic and use 
`org.apache.flink.streaming.api.TimeCharacteristic` directly,
   because StateTtlConfig locates in module flink-core and 
`org.apache.flink.streaming.api.TimeCharacteristic` locates in 
flink-streaming-java,
   so we choice to rename StateTtlConfig#TimeCharacteristic.
   
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (**no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (**no**)
     - The serializers: (**no**)
     - The runtime per-record code paths (performance sensitive): (**no**)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (**no**)
     - The S3 file system connector: (**no**)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (**no**)
     - If yes, how is the feature documented? (**not applicable**)
   

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


With regards,
Apache Git Services

Reply via email to