@Alexander I’m happy to hear that you want to help me. If you help me, I really
appreciate. :)
Regards,
Chiwan Park
> On Jul 2, 2015, at 2:57 PM, Alexander Alexandrov
> wrote:
>
> @Chiwan: let me know if you need hands-on support. I'll be more then happy to
> help (as my downstream project
@Chiwan: let me know if you need hands-on support. I'll be more then happy
to help (as my downstream project is using Scala 2.11).
2015-07-01 17:43 GMT+02:00 Chiwan Park :
> Okay, I will apply this suggestion.
>
> Regards,
> Chiwan Park
>
> > On Jul 1, 2015, at 5:41 PM, Ufuk Celebi wrote:
> >
>
Okay, I will apply this suggestion.
Regards,
Chiwan Park
> On Jul 1, 2015, at 5:41 PM, Ufuk Celebi wrote:
>
>
> On 01 Jul 2015, at 10:34, Stephan Ewen wrote:
>
>> +1, like that approach
>
> +1
>
> I like that this is not breaking for non-Scala users :-)
On 01 Jul 2015, at 10:34, Stephan Ewen wrote:
> +1, like that approach
+1
I like that this is not breaking for non-Scala users :-)
+1, like that approach
On Wed, Jul 1, 2015 at 10:28 AM, Robert Metzger wrote:
> (adding dev@ to the conversation)
>
> Chiwan looked into the issue. It seems that we can not add the Scala
> version only to flink-scala, flink-streaming-scala,
> Since flink-runtime also needs scala all modules
(adding dev@ to the conversation)
Chiwan looked into the issue. It seems that we can not add the Scala
version only to flink-scala, flink-streaming-scala,
Since flink-runtime also needs scala all modules are affected by this.
I would vote for naming the Scala 2.10 version of flink modules wi
I’m interested in working on this. :) I’ll assign to me.
Regards,
Chiwan Park
> On Jun 21, 2015, at 8:22 AM, Robert Metzger wrote:
>
> Okay, it seems like we have consensus on this. Who is interested in working
> on this? https://issues.apache.org/jira/browse/FLINK-2200
>
> On Mon, Jun 15, 2
Okay, it seems like we have consensus on this. Who is interested in working
on this? https://issues.apache.org/jira/browse/FLINK-2200
On Mon, Jun 15, 2015 at 1:26 AM, Till Rohrmann wrote:
> +1 for giving only those modules a version suffix which depend on Scala.
>
>
> On Sun, Jun 14, 2015 at 8:0
+1 for giving only those modules a version suffix which depend on Scala.
On Sun, Jun 14, 2015 at 8:03 PM Robert Metzger wrote:
> There was already a discussion regarding the two options here [1], back
> then we had a majority for giving all modules a scala suffix.
>
> I'm against giving all modu
There was already a discussion regarding the two options here [1], back
then we had a majority for giving all modules a scala suffix.
I'm against giving all modules a suffix because we force our users to
migrate the name and its confusing for Java users (I was confused myself
when I was trying out
Good idea, Chiwan!
On Sat, Jun 13, 2015 at 6:25 PM, Chiwan Park wrote:
> Hi. I think that we don’t need deploy all modules with scala variation.
> The pure java-based modules such as flink-java, flink-core,
> flink-optimizers, …, etc. don’t need to be deployed with scala version
> variation. We
Hi. I think that we don’t need deploy all modules with scala variation. The
pure java-based modules such as flink-java, flink-core, flink-optimizers, …,
etc. don’t need to be deployed with scala version variation. We need only scala
related modules such as flink-ml, flink-runtime, flink-scala, …
I agree that we should ship a 2.11 build of Flink if downstream projects
need that.
The only thing that we should keep in mind when doing this is that the
number of jars we're pushing to maven will explode (but that is fine)
We have currently 46 maven modules and we would create 4 versions of each
Please do ping this list if you encounter any problems with Flink during
your project (you have done so already :-), but also if you find that the
Flink API needs additions to map Pig well to Flink
On Wed, Jun 10, 2015 at 3:47 PM, Philipp Goetze <
philipp.goe...@tu-ilmenau.de> wrote:
> Done. Can
Done. Can be found here: https://issues.apache.org/jira/browse/FLINK-2200
Best Regards,
Philipp
On 10.06.2015 15:29, Chiwan Park wrote:
But I think uploading Flink API with scala 2.11 to maven repository is nice
idea.
Could you create a JIRA issue?
Regards,
Chiwan Park
On Jun 10, 2015, at
But I think uploading Flink API with scala 2.11 to maven repository is nice
idea.
Could you create a JIRA issue?
Regards,
Chiwan Park
> On Jun 10, 2015, at 10:23 PM, Chiwan Park wrote:
>
> No. Currently, there are no Flink binaries with scala 2.11 which are
> downloadable.
>
> Regards,
> Chi
No. Currently, there are no Flink binaries with scala 2.11 which are
downloadable.
Regards,
Chiwan Park
> On Jun 10, 2015, at 10:18 PM, Philipp Goetze
> wrote:
>
> Thank you Chiwan!
>
> I did not know the master has a 2.11 profile.
>
> But there is no pre-built Flink with 2.11, which I coul
No there are no Scala 2.11 Flink binaries which you can download. You have
to build it yourself.
Cheers,
Till
On Wed, Jun 10, 2015 at 3:19 PM Philipp Goetze
wrote:
> Thank you Chiwan!
>
> I did not know the master has a 2.11 profile.
>
> But there is no pre-built Flink with 2.11, which I could
Thank you Chiwan!
I did not know the master has a 2.11 profile.
But there is no pre-built Flink with 2.11, which I could refer to in sbt
or maven, is it?
Best Regards,
Philipp
On 10.06.2015 15:03, Chiwan Park wrote:
Hi. You can build Flink with Scala 2.11 with scala-2.11 profile in master
Hi. You can build Flink with Scala 2.11 with scala-2.11 profile in master
branch.
`mvn clean install -DskipTests -P \!scala-2.10,scala-2.11` command builds Flink
with Scala 2.11.
Regards,
Chiwan Park
> On Jun 10, 2015, at 9:56 PM, Flavio Pompermaier wrote:
>
> Nice!
>
> On 10 Jun 2015 14:49,
Nice!
On 10 Jun 2015 14:49, "Philipp Goetze" wrote:
> Hi community!
>
> We started a new project called Piglet (https://github.com/ksattler/piglet
> ).
> For that we use i.a. Flink as a backend. The project is based on Scala
> 2.11. Thus we need a 2.11 build of Flink.
>
> Until now we used the 2.
21 matches
Mail list logo
