[
https://issues.apache.org/jira/browse/FLINK-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11063:
-----------------------------------
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.
> Make flink-table Scala-free
> ---------------------------
>
> Key: FLINK-11063
> URL: https://issues.apache.org/jira/browse/FLINK-11063
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Affects Versions: 1.7.0
> Reporter: Timo Walther
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Currently, the Table & SQL API is implemented in Scala. This decision was
> made a long-time ago when the initial code base was created as part of a
> master's thesis. The community kept Scala because of the nice language
> features that enable a fluent Table API like {{table.select('field.trim())}}
> and because Scala allows for quick prototyping (e.g. multi-line comments for
> code generation). The committers enforced not splitting the code-base into
> two programming languages.
> However, nowadays the {{flink-table}} module more and more becomes an
> important part in the Flink ecosystem. Connectors, formats, and SQL client
> are actually implemented in Java but need to interoperate with
> {{flink-table}} which makes these modules dependent on Scala. As mentioned in
> an earlier mail thread, using Scala for API classes also exposes member
> variables and methods in Java that should not be exposed to users. Java is
> still the most important API language and right now we treat it as a
> second-class citizen.
> In order to not introduce more technical debt, the community aims to make the
> {{flink-table}} module Scala-free as a long-term goal. This will be a
> continuous effort that can not be finished within one release. We aim for
> avoiding API-breaking changes.
> A full description can be found in the corresponding
> [FLIP-28|https://cwiki.apache.org/confluence/display/FLINK/FLIP-28%3A+Long-term+goal+of+making+flink-table+Scala-free].
> FLIP-28 also contains a rough roadmap and serves as migration guidelines.
> This Jira issue is an umbrella issue for tracking the efforts and possible
> migration blockers.
> *+Update+*: Due to the big code contribution of Alibaba into Flink SQL. We
> will only perform porting of API classes for now. This is mostly tracked by
> FLINK-11448.
> FLIP-28 is legacy and has been integrated into
> [FLIP-32|https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributions].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
