xintongsong opened a new pull request #9910: [FLINK-14406] Align 
ResourceProfile/ResourceSpec fields with the new TaskExecutor memory setups.
URL: https://github.com/apache/flink/pull/9910
 
 
   ## What is the purpose of the change
   
   This PR updates fields of `ResourceProfile` and `ResourceSpec` to align with 
FLIP-49 `TaskExecutor` resources.
   
   ## Brief change log
   - 
d485aedc9c9fb1b851c2b35a3e29fa6b52b13323..af2fc670e561522ea03d35e509408e9695a1a2a0:
 Hot-fixes and clean-ups that should not introduce behavior changes.
     - d485aedc9c9fb1b851c2b35a3e29fa6b52b13323: Introduce `MemorySize` 
constants of special values that are reused a lot.
     - 2b3b9c0b0df581c939147ea4a234cb7b3df99186: Move `SimpleSlotContext` to 
test scope. There's no usage in production codes. This change will allow us to 
annotate `ResourceProfile#ANY` as for test purpose only.
     - 9b5ec1eb9ef812871a0b8d02cd258ffa12adb80b: Fix misusage of 
`ResourceProfile#UNKNOWN` and `ResourceProfile#ANY`, and rename `ANY` to 
`INFINITE` for readability.
     - af2fc670e561522ea03d35e509408e9695a1a2a0: Disable numerical comparing  
`ResourceProfile#UNKNOWN`.
   - 8d1696b97872fdd9fd3aca725c8b58ad8227f6f2: Update `ResourceProfile` and 
`ResourceSpec` fields to align with FLIP-49 `TaskExecutor` resources.
   
   ## Verifying this change
   This change is already covered by existing tests, such as 
`ResourceProfileTest` and `ResourceSpecTest`. This PR updates the existing 
tests to align with the new fields.
   
   ## 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)`: (yes)
     - 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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to