Akshay and Ankit,
Scala support is definitely in our roadmap.
Akshay,
The exception you see might be related to some Scala function that compiled
to java anonymous class. There are 2 possible workarounds (I haven't tried
but possibly they would work).
1. You can try move your functional expression(A => B) to a
well-defined class.
2. Use some third-party kryo serializer for scala classes(
https://github.com/twitter/chill) and annotate on that functional field(
@Bind(SomeScalaSerializer.class)
Please let us know if any of them works :)
Ankit,
Resolve dependency and compile the code should not be the problem, the
problem is the assembly plugin seems work different from the plugin in
maven and we need to work on that part. You can also try gradle which has
more features and support both scala and maven very well. You are very
welcome to lead and contribute to the community! :)
Regards,
Siyuan
On Thu, Jul 14, 2016 at 11:14 PM, Ankit Sarraf <[email protected]>
wrote:
> Interesting. Thanks for sharing the link. I surly feel that if DataTorrent
> has to expand its roots, it will have to evolve to support as many
> languages seamlessly as possible. So it seems to have complete support for
> Scala in future.
>
> Also, curious to know if people at DT are thinking of allowing SBT
> application build with the apps?
>
> On Jul 14, 2016 11:07 PM, "Akshay S Harale" <[email protected]>
> wrote:
>
> Hello,
>
> I found one blog post on writing apex app in scala
> <https://www.datatorrent.com/blog/blog-writing-apache-apex-application-in-scala/>.
> First I tried simple app it worked very well but when I introduced some
> anonymous functions in program, it started throwing kryo serialisation
> exception:
> *com.esotericsoftware.kryo.KryoException: Class cannot be created (missing
> no-arg constructor): com.sample.Aggregator$$anon$1*
>
> My question is : Will Apex have full support for scala in future ?
>
> Regards,
> Akshay S. Harale
> Software Developer @ Synerzip
> Skype – akshayharale
>
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient. Any
> review, use, distribution, or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.
>
>
>
