The JIRA issue is FLINK-3610.
On Sat, Mar 12, 2016 at 8:39 PM, Márton Balassi
wrote:
>
> I have just come across a shortcoming of the streaming Scala API: it
> completely lacks the Scala implementation of the DataStreamSink and
> instead the Java version is used. [1]
>
> I would regard this as a
Márton Balassi created FLINK-3610:
-
Summary: Scala DataStream#addSink returns Java DataStreamSink
Key: FLINK-3610
URL: https://issues.apache.org/jira/browse/FLINK-3610
Project: Flink
Issue Ty
Hey,
I have just come across a shortcoming of the streaming Scala API: it
completely lacks the Scala implementation of the DataStreamSink and instead
the Java version is used. [1]
I would regard this as a bug that needs a fix for 1.0.1. Unfortunately this
is also api-breaking.
Will post it to JI
Thanks for the insight, what you're doing is really interesting. I will
definitely spend some time looking at DMLC and MXNet.
2016-03-12 18:35 GMT+01:00 Tianqi Chen :
> Thanks for the reply. I am writing a long email to give the answers to
> Simone and clarifies what we do
>
> I want to mention
Thanks for the reply. I am writing a long email to give the answers to
Simone and clarifies what we do
I want to mention that *you can use the library already in Flink*. See
Flink example here:
https://github.com/dmlc/xgboost/tree/master/jvm-packages#xgboost-flink
I have not run pressure test on
Hello Tianqui,
Yes that definitely sounds interesting for us and we are looking forward to
help out with the implementation.
Regards,
Theodore
--
Sent from a mobile device. May contain autocorrect errors.
On Mar 12, 2016 11:29 AM, "Simone Robutti"
wrote:
> This is a really interesting approach
This is a really interesting approach. The idea of a ML library over
DataFlow is probably a winning move and I hope it will stop the
proliferation of worthless reimplementation that is taking place in the big
data world. Do you think that DataFlow posed specific problems to your
work? Does it missi
