wuchong opened a new pull request #7906: [FLINK-11830][table-planner-blink] 
Introduce CodeGeneratorContext to maintain reusable statements
URL: https://github.com/apache/flink/pull/7906
 
 
   
   ## What is the purpose of the change
   
   Introduce `CodeGeneratorContext` to maintain reusable statements for code 
generation.
   
   The `CodeGeneratorContext` will keep all the reusable statements which will 
be the basic class for code generation. In the future, we will introduce 
FunctionCodeGeneration, AggregateCodeGeneration, etc... and they will depend on 
the `CodeGeneratorContext` to store reusable statements.
   
   
   ## Brief change log
   
     - Introduce `CodeGeneratorContext`.
     - Introduce `CompileUtils` in `table-runtime-blink` to support compile 
code in runtime.
     - Introduce `GeneratedClass` in `table-runtime-blink` to wrap generated 
code and class name to support easy instantiation.
     - Copy `TableConfig` to `table-planner-blink` because 
`CodeGeneratorContext` depends on it.
     - Introduce `CodeGenUtils` to package utilities for codegen (will add 
various `generateXXX` in FLINK-11788).
     - Introduce `TypeCheckUtils` to check types. 
   
   ## Verifying this change
   
   The `CodeGeneratorContext` will be covered in later FLINK-11788.
   
   Added a `CompileUtilsTest` to test compile classes with cache.
   
   ## 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