[
https://issues.apache.org/jira/browse/FLINK-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11831:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Separate CodeGeneratorContext for different generation targets
> --------------------------------------------------------------
>
> Key: FLINK-11831
> URL: https://issues.apache.org/jira/browse/FLINK-11831
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Runtime
> Reporter: Kurt Young
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Currently, we have one big `CodeGeneratorContext` during code generation, it
> contains all possible reused statements even for different code generation
> targets. For example, when we want to codeden a `Function`, we may use the
> `reusableOpenStatements` and `reusableCloseStatements`. And when we codegen
> an operator, we will use something like `reusableEndInputStatements`. It is
> error prone and hard to know what should be placed into codegened classes and
> what shouldn't.
>
> I think we should have dedicated context for each codegen class. Like
> `FunctionCodegenContext` and `OperatorCodegenContext`, they can share a base
> class to reuse some common requirements, like reused class members.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
