Hi,
you are right. Having two languages in the code base doesn't make our
lives easier. But Flink is a big project with a long history, multiple
design shifts, and many contributors. It is naturally that the bigger a
code base gets, the messier it looks like. It must be a continuous
effort to improve legacy code.
We are aiming to have Scala only in dedicated API modules. We encourage
people to choose Java whenever new code is developed or refactored. So
eventually, Flink might be Scala free but this will take some time.
For example, we have already dedicated porting guidelines for the
flink-table module [1][2]. I'm sure other component maintainers have
similar thoughts.
Regards,
Timo
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-28%3A+Long-term+goal+of+making+flink-table+Scala-free[2]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributionsOn 19.09.20 16:21, 490548661 wrote:
> The Flink code is too messy. It uses both Java and scala.
> Can you unify the language and use Java only . Is it not tiring to maintain two sets of codes
>