apex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yogi Devendra <yogideven...@apache.org>
Subject Re: Regarding using Scala to develop Apex app.
Date Fri, 15 Jul 2016 09:32:33 GMT
Akshay, Ankit

Yes. Apex would have full support for scala in future. We understand that
many developers would love to use scala or python binding. We would
definitely consider this as a user feedback and it will be funneled through
the items listed for the project roadmap.

But, it would be hard to give specific timeline regarding this. Priorities
are decided based on the importance of the feature as well as number of
people are asking for it.

On a side note, you can also contribute on this effort.

~ Yogi

On 15 July 2016 at 11:44, Ankit Sarraf <ankit.sarraf@cloudwick.com> 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" <akshay.harale@synerzip.com>
> 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.

View raw message