[
https://issues.apache.org/jira/browse/SAMZA-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821325#comment-16821325
]
Cameron Lee commented on SAMZA-2166:
------------------------------------
Hey [~Tison],
I don't think there is an umbrella issue around this. My understanding of the
community consensus is that any new code should be in Java, but we will
continue to support the existing Scala classes and minor changes/additions to
existing Scala classes are ok.
Personally, I would like to ultimately see everything move to Java. It has been
a painpoint maintaining multiple versions of Scala support, and some of the
Scala-Java code interactions are a little awkward. I have been looking for
certain areas of Samza in which the usage of Scala is more significantly
unclean and occasionally will try to do some refactoring. The current area I
have been looking at is these config-related classes, where we sometimes have
separate Scala and Java classes for the same type of config. Those separate
classes should be consolidated.
Cameron
> [Scala cleanup] Convert StorageConfig.scala to Java
> ---------------------------------------------------
>
> Key: SAMZA-2166
> URL: https://issues.apache.org/jira/browse/SAMZA-2166
> Project: Samza
> Issue Type: Improvement
> Reporter: Cameron Lee
> Assignee: Cameron Lee
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It has been challenging to maintain Scala code alongside Java code.
> Starting to do some Scala cleanup to consolidate code into Java. For example,
> there is a StorageConfig.scala and a JavaStorageConfig.java. This
> consolidates those into a single StorageConfig.java.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
