Re: [DISCUSS] Scala code style - explicit vs implicit code behavior

2015-02-16 Thread Aljoscha Krettek
+1

On Mon, Feb 16, 2015 at 3:18 PM, Fabian Hueske  wrote:
> +1
>
> 2015-02-15 17:47 GMT+01:00 Stephan Ewen :
>
>> I thought about adding a wiki page for that.
>>
>> On Sat, Feb 14, 2015 at 7:16 PM, Henry Saputra 
>> wrote:
>>
>> > +1 to the idea
>> >
>> > I suppose no really action item for FLINK-1548? Maybe add doc about
>> > contributing to Scala portion?
>> >
>> >
>> > On Saturday, February 14, 2015, Stephan Ewen  wrote:
>> >
>> > > Hi everyone!
>> > >
>> > > Since a sizable portion of the Flink code is now in Scala (and more is
>> > > coming in the API projects), I think we need to define a few guidelines
>> > for
>> > > Scala programming.
>> > >
>> > > Scala is very powerful and has a lot of "magic" features that allow you
>> > to
>> > > design killer nice APIs, but also make reasoning about code harder.
>> > > Through the use of implicit parameters, lazy parameters, overriding of
>> > base
>> > > operators, functions that take code blocks, etc, you can easily write
>> > code
>> > > that does something entirely different than what it looks like
>> initially.
>> > >
>> > > For APIs, I think we should embrace the power of these features to make
>> > the
>> > > APIs nice, convenient, and with intuitive syntax. After all, the
>> elegance
>> > > of the API matters a lot.
>> > >
>> > > For the runtime or anything below the APIs, I propose to refrain to a
>> > large
>> > > extend from the magic features. For those parts, I think it matters
>> most
>> > > that the code is predictable, it is easy to understand the implications
>> > for
>> > > also non-expert Scala programmers, and it is possible to peer review it
>> > > through GitHub (where you do not see a difference between a lazy or an
>> > > eager parameter).
>> > >
>> > > One example of such a change would be
>> > > https://issues.apache.org/jira/browse/FLINK-1548
>> > >
>> > > Summary: Be magic in the APIs, be explicit and simple in the runtime.
>> > >
>> > > Greetings,
>> > > Stephan
>> > >
>> >
>>


[VOTE] Release Apache Flink 0.8.1 (RC2)

2015-02-16 Thread Robert Metzger
Please vote on releasing the following candidate as Apache Flink version
0.8.1

Please check the release carefully. There were quite a few last-minute fixes

This is a bugfix release for 0.8.0.

-
The commit to be voted on is in the branch "release-0.8.1-rc2"
(commit b35e7460
):
http://git-wip-us.apache.org/repos/asf/flink/commit/b35e7460

The release artifacts to be voted on can be found at:
http://people.apache.org/~rmetzger/flink-0.8.1-rc2/

Release artifacts are signed with the following key:
*https://people.apache.org/keys/committer/rmetzger.asc
*

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/orgapacheflink-1033
-


Please vote on releasing this package as Apache Flink 0.8.1.

The vote is open for the next 72 hours and passes if a majority of at least
three +1 PMC votes are cast.
The vote will end on Wednesday.

[ ] +1 Release this package as Apache Flink 0.8.1
[ ] -1 Do not release this package because ...


[jira] [Created] (FLINK-1555) Add utility to log the serializers of composite types

2015-02-16 Thread Robert Metzger (JIRA)
Robert Metzger created FLINK-1555:
-

 Summary: Add utility to log the serializers of composite types
 Key: FLINK-1555
 URL: https://issues.apache.org/jira/browse/FLINK-1555
 Project: Flink
  Issue Type: Improvement
Reporter: Robert Metzger
Priority: Minor


Users affected by poor performance might want to understand how Flink is 
serializing their data.

Therefore, it would be cool to have a tool utility which logs the serializers 
like this:
{{SerializerUtils.getSerializers(TypeInformation t);}}
to get 
{code}
PojoSerializer
TupleSerializer
  IntSer
  DateSer
  GenericTypeSer(java.sql.Date)
PojoSerializer
  GenericTypeSer(HashMap)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [DISCUSS] Scala code style - explicit vs implicit code behavior

2015-02-16 Thread Till Rohrmann
+1

On Mon, Feb 16, 2015 at 3:38 PM, Aljoscha Krettek 
wrote:

> +1
>
> On Mon, Feb 16, 2015 at 3:18 PM, Fabian Hueske  wrote:
> > +1
> >
> > 2015-02-15 17:47 GMT+01:00 Stephan Ewen :
> >
> >> I thought about adding a wiki page for that.
> >>
> >> On Sat, Feb 14, 2015 at 7:16 PM, Henry Saputra  >
> >> wrote:
> >>
> >> > +1 to the idea
> >> >
> >> > I suppose no really action item for FLINK-1548? Maybe add doc about
> >> > contributing to Scala portion?
> >> >
> >> >
> >> > On Saturday, February 14, 2015, Stephan Ewen 
> wrote:
> >> >
> >> > > Hi everyone!
> >> > >
> >> > > Since a sizable portion of the Flink code is now in Scala (and more
> is
> >> > > coming in the API projects), I think we need to define a few
> guidelines
> >> > for
> >> > > Scala programming.
> >> > >
> >> > > Scala is very powerful and has a lot of "magic" features that allow
> you
> >> > to
> >> > > design killer nice APIs, but also make reasoning about code harder.
> >> > > Through the use of implicit parameters, lazy parameters, overriding
> of
> >> > base
> >> > > operators, functions that take code blocks, etc, you can easily
> write
> >> > code
> >> > > that does something entirely different than what it looks like
> >> initially.
> >> > >
> >> > > For APIs, I think we should embrace the power of these features to
> make
> >> > the
> >> > > APIs nice, convenient, and with intuitive syntax. After all, the
> >> elegance
> >> > > of the API matters a lot.
> >> > >
> >> > > For the runtime or anything below the APIs, I propose to refrain to
> a
> >> > large
> >> > > extend from the magic features. For those parts, I think it matters
> >> most
> >> > > that the code is predictable, it is easy to understand the
> implications
> >> > for
> >> > > also non-expert Scala programmers, and it is possible to peer
> review it
> >> > > through GitHub (where you do not see a difference between a lazy or
> an
> >> > > eager parameter).
> >> > >
> >> > > One example of such a change would be
> >> > > https://issues.apache.org/jira/browse/FLINK-1548
> >> > >
> >> > > Summary: Be magic in the APIs, be explicit and simple in the
> runtime.
> >> > >
> >> > > Greetings,
> >> > > Stephan
> >> > >
> >> >
> >>
>


[jira] [Created] (FLINK-1556) JobClient does not wait until a job failed completely if submission exception

2015-02-16 Thread Till Rohrmann (JIRA)
Till Rohrmann created FLINK-1556:


 Summary: JobClient does not wait until a job failed completely if 
submission exception
 Key: FLINK-1556
 URL: https://issues.apache.org/jira/browse/FLINK-1556
 Project: Flink
  Issue Type: Bug
Reporter: Till Rohrmann


If an exception occurs during job submission the {{JobClient}} received a 
{{SubmissionFailure}}. Upon receiving this message, the {{JobClient}} 
terminates itself and returns the error to the {{Client}}. This indicates to 
the user that the job has been completely failed which is not necessarily true. 

If the user directly after such a failure submits another job, then it might be 
the case that not all slots of the formerly failed job are returned. This can 
lead to a {{NoRessourceAvailableException}}.

We can solve this problem by waiting for the completion of the job failure in 
the {{JobClient}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [DISCUSS] Scala code style - explicit vs implicit code behavior

2015-02-16 Thread Paris Carbone
+1

Good point. In general, keeping the common/runtime as simple as possible is 
quite important

> On 16 Feb 2015, at 16:05, Till Rohrmann  wrote:
> 
> +1
> 
> On Mon, Feb 16, 2015 at 3:38 PM, Aljoscha Krettek 
> wrote:
> 
>> +1
>> 
>> On Mon, Feb 16, 2015 at 3:18 PM, Fabian Hueske  wrote:
>>> +1
>>> 
>>> 2015-02-15 17:47 GMT+01:00 Stephan Ewen :
>>> 
 I thought about adding a wiki page for that.
 
 On Sat, Feb 14, 2015 at 7:16 PM, Henry Saputra >> 
 wrote:
 
> +1 to the idea
> 
> I suppose no really action item for FLINK-1548? Maybe add doc about
> contributing to Scala portion?
> 
> 
> On Saturday, February 14, 2015, Stephan Ewen 
>> wrote:
> 
>> Hi everyone!
>> 
>> Since a sizable portion of the Flink code is now in Scala (and more
>> is
>> coming in the API projects), I think we need to define a few
>> guidelines
> for
>> Scala programming.
>> 
>> Scala is very powerful and has a lot of "magic" features that allow
>> you
> to
>> design killer nice APIs, but also make reasoning about code harder.
>> Through the use of implicit parameters, lazy parameters, overriding
>> of
> base
>> operators, functions that take code blocks, etc, you can easily
>> write
> code
>> that does something entirely different than what it looks like
 initially.
>> 
>> For APIs, I think we should embrace the power of these features to
>> make
> the
>> APIs nice, convenient, and with intuitive syntax. After all, the
 elegance
>> of the API matters a lot.
>> 
>> For the runtime or anything below the APIs, I propose to refrain to
>> a
> large
>> extend from the magic features. For those parts, I think it matters
 most
>> that the code is predictable, it is easy to understand the
>> implications
> for
>> also non-expert Scala programmers, and it is possible to peer
>> review it
>> through GitHub (where you do not see a difference between a lazy or
>> an
>> eager parameter).
>> 
>> One example of such a change would be
>> https://issues.apache.org/jira/browse/FLINK-1548
>> 
>> Summary: Be magic in the APIs, be explicit and simple in the
>> runtime.
>> 
>> Greetings,
>> Stephan
>> 
> 
 
>> 



Re: [VOTE] Release Apache Flink 0.8.1 (RC2)

2015-02-16 Thread Fabian Hueske
- checked all checksums and signatures
- checked running examples with build-in data on local setup on Windows 8.1
(hadoop1.tgz, hadoop2.tgz)

2015-02-16 15:54 GMT+01:00 Robert Metzger :

> Please vote on releasing the following candidate as Apache Flink version
> 0.8.1
>
> Please check the release carefully. There were quite a few last-minute
> fixes
>
> This is a bugfix release for 0.8.0.
>
> -
> The commit to be voted on is in the branch "release-0.8.1-rc2"
> (commit b35e7460
> ):
> http://git-wip-us.apache.org/repos/asf/flink/commit/b35e7460
>
> The release artifacts to be voted on can be found at:
> http://people.apache.org/~rmetzger/flink-0.8.1-rc2/
>
> Release artifacts are signed with the following key:
> *https://people.apache.org/keys/committer/rmetzger.asc
> *
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapacheflink-1033
> -
>
>
> Please vote on releasing this package as Apache Flink 0.8.1.
>
> The vote is open for the next 72 hours and passes if a majority of at least
> three +1 PMC votes are cast.
> The vote will end on Wednesday.
>
> [ ] +1 Release this package as Apache Flink 0.8.1
> [ ] -1 Do not release this package because ...
>


[jira] [Created] (FLINK-1557) Move WebFrontend out of JobManager Actor

2015-02-16 Thread Stephan Ewen (JIRA)
Stephan Ewen created FLINK-1557:
---

 Summary: Move WebFrontend out of JobManager Actor
 Key: FLINK-1557
 URL: https://issues.apache.org/jira/browse/FLINK-1557
 Project: Flink
  Issue Type: Improvement
  Components: JobManager
Affects Versions: 0.9
Reporter: Stephan Ewen
Assignee: Stephan Ewen
 Fix For: 0.9


Currently, the Webfrontent is started inside the JobManager actor.

I propose to move it out of the actor, since it is a heavy component that is 
independent of the actor and whose failure cannot be controlled by the job 
manager.

The change is fairly straightforward, since the web frontend only communicates 
with the jobmanager through actor messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (FLINK-1558) Spurious failure in PipelinedPartitionQueueTest

2015-02-16 Thread Stephan Ewen (JIRA)
Stephan Ewen created FLINK-1558:
---

 Summary: Spurious failure in PipelinedPartitionQueueTest
 Key: FLINK-1558
 URL: https://issues.apache.org/jira/browse/FLINK-1558
 Project: Flink
  Issue Type: Improvement
  Components: Distributed Runtime
Affects Versions: 0.9
Reporter: Stephan Ewen
 Fix For: 0.9


The failure is reported as
{code}
java.lang.AssertionError: Unexpected failure during test: null. Producer error: 
null, consumer error: null
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.flink.runtime.io.network.partition.queue.PipelinedPartitionQueueTest.doTestConcurrentProduceConsume(PipelinedPartitionQueueTest.java:214)
at 
org.apache.flink.runtime.io.network.partition.queue.PipelinedPartitionQueueTest.doTestConcurrentProduceConsume(PipelinedPartitionQueueTest.java:171)
at 
org.apache.flink.runtime.io.network.partition.queue.PipelinedPartitionQueueTest.testConcurrentProduceConsume(PipelinedPartitionQueueTest.java:142)
{code}

The test shows the following stack trace
{code}
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:258)
at java.util.concurrent.FutureTask.get(FutureTask.java:119)
at 
org.apache.flink.runtime.io.network.partition.queue.PipelinedPartitionQueueTest.doTestConcurrentProduceConsume(PipelinedPartitionQueueTest.java:198)
at 
org.apache.flink.runtime.io.network.partition.queue.PipelinedPartitionQueueTest.doTestConcurrentProduceConsume(PipelinedPartitionQueueTest.java:171)
at 
org.apache.flink.runtime.io.network.partition.queue.PipelinedPartitionQueueTest.testConcurrentProduceConsume(PipelinedPartitionQueueTest.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [VOTE] Release Apache Flink 0.8.1 (RC2)

2015-02-16 Thread Stephan Ewen
+1

 - All versions are correct
 - No binaries in the release
 - License headers are good
 - Verified that LICENSE and NOTICE files reflect the source and binary
dependencies accordingly
 - Readme looks good, URLs refer to post-graduation website
 - code compiles, all tests pass
 - ran examples in local mode
 - ran examples in a local 2 node cluster
 - checked plan visualizer standalone
 - checked plan visualizer web frontend
 - validated log output - no error messages encountered

Good release all in all :-)


On Mon, Feb 16, 2015 at 4:38 PM, Fabian Hueske  wrote:

> - checked all checksums and signatures
> - checked running examples with build-in data on local setup on Windows 8.1
> (hadoop1.tgz, hadoop2.tgz)
>
> 2015-02-16 15:54 GMT+01:00 Robert Metzger :
>
> > Please vote on releasing the following candidate as Apache Flink version
> > 0.8.1
> >
> > Please check the release carefully. There were quite a few last-minute
> > fixes
> >
> > This is a bugfix release for 0.8.0.
> >
> > -
> > The commit to be voted on is in the branch "release-0.8.1-rc2"
> > (commit b35e7460
> > ):
> > http://git-wip-us.apache.org/repos/asf/flink/commit/b35e7460
> >
> > The release artifacts to be voted on can be found at:
> > http://people.apache.org/~rmetzger/flink-0.8.1-rc2/
> >
> > Release artifacts are signed with the following key:
> > *https://people.apache.org/keys/committer/rmetzger.asc
> > *
> >
> > The staging repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapacheflink-1033
> > -
> >
> >
> > Please vote on releasing this package as Apache Flink 0.8.1.
> >
> > The vote is open for the next 72 hours and passes if a majority of at
> least
> > three +1 PMC votes are cast.
> > The vote will end on Wednesday.
> >
> > [ ] +1 Release this package as Apache Flink 0.8.1
> > [ ] -1 Do not release this package because ...
> >
>


Re: [VOTE] Release Apache Flink 0.8.1 (RC2)

2015-02-16 Thread Fabian Hueske
+1 (forgot that earlier)

2015-02-16 17:03 GMT+01:00 Stephan Ewen :

> +1
>
>  - All versions are correct
>  - No binaries in the release
>  - License headers are good
>  - Verified that LICENSE and NOTICE files reflect the source and binary
> dependencies accordingly
>  - Readme looks good, URLs refer to post-graduation website
>  - code compiles, all tests pass
>  - ran examples in local mode
>  - ran examples in a local 2 node cluster
>  - checked plan visualizer standalone
>  - checked plan visualizer web frontend
>  - validated log output - no error messages encountered
>
> Good release all in all :-)
>
>
> On Mon, Feb 16, 2015 at 4:38 PM, Fabian Hueske  wrote:
>
> > - checked all checksums and signatures
> > - checked running examples with build-in data on local setup on Windows
> 8.1
> > (hadoop1.tgz, hadoop2.tgz)
> >
> > 2015-02-16 15:54 GMT+01:00 Robert Metzger :
> >
> > > Please vote on releasing the following candidate as Apache Flink
> version
> > > 0.8.1
> > >
> > > Please check the release carefully. There were quite a few last-minute
> > > fixes
> > >
> > > This is a bugfix release for 0.8.0.
> > >
> > > -
> > > The commit to be voted on is in the branch "release-0.8.1-rc2"
> > > (commit b35e7460
> > > ):
> > > http://git-wip-us.apache.org/repos/asf/flink/commit/b35e7460
> > >
> > > The release artifacts to be voted on can be found at:
> > > http://people.apache.org/~rmetzger/flink-0.8.1-rc2/
> > >
> > > Release artifacts are signed with the following key:
> > > *https://people.apache.org/keys/committer/rmetzger.asc
> > > *
> > >
> > > The staging repository for this release can be found at:
> > > https://repository.apache.org/content/repositories/orgapacheflink-1033
> > > -
> > >
> > >
> > > Please vote on releasing this package as Apache Flink 0.8.1.
> > >
> > > The vote is open for the next 72 hours and passes if a majority of at
> > least
> > > three +1 PMC votes are cast.
> > > The vote will end on Wednesday.
> > >
> > > [ ] +1 Release this package as Apache Flink 0.8.1
> > > [ ] -1 Do not release this package because ...
> > >
> >
>


[jira] [Created] (FLINK-1559) Normalize all Akka URLs to use IP addresses, not hostnames

2015-02-16 Thread Stephan Ewen (JIRA)
Stephan Ewen created FLINK-1559:
---

 Summary: Normalize all Akka URLs to use IP addresses, not hostnames
 Key: FLINK-1559
 URL: https://issues.apache.org/jira/browse/FLINK-1559
 Project: Flink
  Issue Type: Bug
  Components: Distributed Runtime
Affects Versions: 0.9
Reporter: Stephan Ewen
Assignee: Stephan Ewen
 Fix For: 0.9


Akka has the nasty property that it does not use IP addresses and hostnames 
interchangeably. 

Example: If the JobManager is started at 
{{akka:tcp//flink@localhost:1234/user/JOBMANAGER}} and a job client actor tries 
to send messages to {{akka:tcp//flink@127.0.0.1:1234/user/JOBMANAGER}}, the job 
manager actor system will receive the messages, but throw them away, because 
they are not destined for the actor system.

I am not sure whether this is a bug or a feature in akka, but we need to deal 
with it. To be on the safe side, I suggest to build all akka URLs with ip 
addresses. We can still use host names in our logic (connection infos, local 
assignments, etc)




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (FLINK-1560) Add ITCases for streaming examples

2015-02-16 Thread JIRA
Márton Balassi created FLINK-1560:
-

 Summary: Add ITCases for streaming examples
 Key: FLINK-1560
 URL: https://issues.apache.org/jira/browse/FLINK-1560
 Project: Flink
  Issue Type: Test
  Components: Streaming
Affects Versions: 0.9
Reporter: Márton Balassi
Assignee: Márton Balassi


Currently there are no tests for consistency of the streaming example programs. 
This might be a real show stopper for users who encounter an issue there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (FLINK-1553) Kafka connectors rework

2015-02-16 Thread JIRA
Gábor Hermann created FLINK-1553:


 Summary: Kafka connectors rework
 Key: FLINK-1553
 URL: https://issues.apache.org/jira/browse/FLINK-1553
 Project: Flink
  Issue Type: Bug
  Components: Streaming
Reporter: Gábor Hermann
Assignee: Gábor Hermann


The Kafka connectors should be reworked and tested because it is not fully 
functioning (e.g. the source can only read partitions from the start).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [VOTE] Release Apache Flink 0.8.1 (RC1)

2015-02-16 Thread Stephan Ewen
-1

I think we should go for quality - even minor tools should work.
Let's quickly fix this and throw out a new release candidate.

On Sun, Feb 15, 2015 at 7:00 PM, Stephan Ewen  wrote:

> The release is good, except for the fact that the standalone plan
> visualizer tool is broken.
>
> Since this is the first test, I would actually like to stop the vote and
> fix the release, it is a minor issue, I'll open a pull request immediately.
> I am not adamant on this, though, because it affects only a minor util, not
> a core component of the system. If the majority votes to proceed, I am
> okay.
>
> Verified the following:
>
>  - All versions are correct
>  - No binaries in the release
>  - License headers are good
>  - Verified that LICENSE and NOTICE files reflect the source and binary
> dependencies accordingly
>  - Readme looks good, URLs refer to post-graduation website
>  - code compiles, all tests pass
>  - ran examples in local mode
>  - ran examples in a local 2 node cluster
>  - checked plan visualizer standalone
>  - checked plan visualizer web frontend
>  - validated log output - no error messages encountered
>
>
> Minor issues:
>  - directory with examples contains the
> "flink-java-examples-0.8.1-javadoc.jar" file
>  - Web server logs about "Nephele"
>
>
>
> On Fri, Feb 13, 2015 at 9:50 AM, Robert Metzger 
> wrote:
>
>> Please vote on releasing the following candidate as Apache Flink version
>> 0.8.1
>>
>> Please check the release carefully. There were quite a few last-minute
>> quickfixes
>>
>> This is a bugfix release for 0.8.0.
>>
>> -
>> The commit to be voted on is in the branch "release-0.8.1-rc1"
>> (commit bf1d877c
>> ):
>> http://git-wip-us.apache.org/repos/asf/flink/commit/bf1d877c
>>
>> The release artifacts to be voted on can be found at:
>> http://people.apache.org/~rmetzger/flink-0.8.1-rc1/
>>
>> Release artifacts are signed with the following key:
>> *https://people.apache.org/keys/committer/rmetzger.asc
>> *
>>
>> The staging repository for this release can be found at:
>> https://repository.apache.org/content/repositories/orgapacheflink-1032
>> -
>>
>>
>> Please vote on releasing this package as Apache Flink 0.8.1.
>>
>> The vote is open for the next 72 hours and passes if a majority of at
>> least
>> three +1 PMC votes are cast.
>> Please note that we don't account for the weekend, so the vote ends on
>> Tuesday.
>>
>> [ ] +1 Release this package as Apache Flink 0.8.1
>> [ ] -1 Do not release this package because ...
>>
>
>


[CANCEL] [VOTE] Release Apache Flink 0.8.1 (RC1)

2015-02-16 Thread Robert Metzger
I hereby cancel the vote.

It seems that the issue has been fixed in the release-0.8 branch:
https://github.com/apache/flink/commit/eec39a2da8c0d83e8edb0d4dad320bd8f683b852

I'll create a new RC.

On Mon, Feb 16, 2015 at 1:16 PM, Stephan Ewen  wrote:

> -1
>
> I think we should go for quality - even minor tools should work.
> Let's quickly fix this and throw out a new release candidate.
>
> On Sun, Feb 15, 2015 at 7:00 PM, Stephan Ewen  wrote:
>
> > The release is good, except for the fact that the standalone plan
> > visualizer tool is broken.
> >
> > Since this is the first test, I would actually like to stop the vote and
> > fix the release, it is a minor issue, I'll open a pull request
> immediately.
> > I am not adamant on this, though, because it affects only a minor util,
> not
> > a core component of the system. If the majority votes to proceed, I am
> > okay.
> >
> > Verified the following:
> >
> >  - All versions are correct
> >  - No binaries in the release
> >  - License headers are good
> >  - Verified that LICENSE and NOTICE files reflect the source and binary
> > dependencies accordingly
> >  - Readme looks good, URLs refer to post-graduation website
> >  - code compiles, all tests pass
> >  - ran examples in local mode
> >  - ran examples in a local 2 node cluster
> >  - checked plan visualizer standalone
> >  - checked plan visualizer web frontend
> >  - validated log output - no error messages encountered
> >
> >
> > Minor issues:
> >  - directory with examples contains the
> > "flink-java-examples-0.8.1-javadoc.jar" file
> >  - Web server logs about "Nephele"
> >
> >
> >
> > On Fri, Feb 13, 2015 at 9:50 AM, Robert Metzger 
> > wrote:
> >
> >> Please vote on releasing the following candidate as Apache Flink version
> >> 0.8.1
> >>
> >> Please check the release carefully. There were quite a few last-minute
> >> quickfixes
> >>
> >> This is a bugfix release for 0.8.0.
> >>
> >> -
> >> The commit to be voted on is in the branch "release-0.8.1-rc1"
> >> (commit bf1d877c
> >> ):
> >> http://git-wip-us.apache.org/repos/asf/flink/commit/bf1d877c
> >>
> >> The release artifacts to be voted on can be found at:
> >> http://people.apache.org/~rmetzger/flink-0.8.1-rc1/
> >>
> >> Release artifacts are signed with the following key:
> >> *https://people.apache.org/keys/committer/rmetzger.asc
> >> *
> >>
> >> The staging repository for this release can be found at:
> >> https://repository.apache.org/content/repositories/orgapacheflink-1032
> >> -
> >>
> >>
> >> Please vote on releasing this package as Apache Flink 0.8.1.
> >>
> >> The vote is open for the next 72 hours and passes if a majority of at
> >> least
> >> three +1 PMC votes are cast.
> >> Please note that we don't account for the weekend, so the vote ends on
> >> Tuesday.
> >>
> >> [ ] +1 Release this package as Apache Flink 0.8.1
> >> [ ] -1 Do not release this package because ...
> >>
> >
> >
>


[jira] [Created] (FLINK-1554) LocalFlinkMiniCluster cannot start multiple local TaskManagers

2015-02-16 Thread Till Rohrmann (JIRA)
Till Rohrmann created FLINK-1554:


 Summary: LocalFlinkMiniCluster cannot start multiple local 
TaskManagers
 Key: FLINK-1554
 URL: https://issues.apache.org/jira/browse/FLINK-1554
 Project: Flink
  Issue Type: Bug
Reporter: Till Rohrmann


The {{LocalFlinkMiniCluster}} cannot currently start multiple {{TaskManager}}s 
in the same {{ActorSystem}}, because it assigns them the same actor name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [DISCUSS] Scala code style - explicit vs implicit code behavior

2015-02-16 Thread Fabian Hueske
+1

2015-02-15 17:47 GMT+01:00 Stephan Ewen :

> I thought about adding a wiki page for that.
>
> On Sat, Feb 14, 2015 at 7:16 PM, Henry Saputra 
> wrote:
>
> > +1 to the idea
> >
> > I suppose no really action item for FLINK-1548? Maybe add doc about
> > contributing to Scala portion?
> >
> >
> > On Saturday, February 14, 2015, Stephan Ewen  wrote:
> >
> > > Hi everyone!
> > >
> > > Since a sizable portion of the Flink code is now in Scala (and more is
> > > coming in the API projects), I think we need to define a few guidelines
> > for
> > > Scala programming.
> > >
> > > Scala is very powerful and has a lot of "magic" features that allow you
> > to
> > > design killer nice APIs, but also make reasoning about code harder.
> > > Through the use of implicit parameters, lazy parameters, overriding of
> > base
> > > operators, functions that take code blocks, etc, you can easily write
> > code
> > > that does something entirely different than what it looks like
> initially.
> > >
> > > For APIs, I think we should embrace the power of these features to make
> > the
> > > APIs nice, convenient, and with intuitive syntax. After all, the
> elegance
> > > of the API matters a lot.
> > >
> > > For the runtime or anything below the APIs, I propose to refrain to a
> > large
> > > extend from the magic features. For those parts, I think it matters
> most
> > > that the code is predictable, it is easy to understand the implications
> > for
> > > also non-expert Scala programmers, and it is possible to peer review it
> > > through GitHub (where you do not see a difference between a lazy or an
> > > eager parameter).
> > >
> > > One example of such a change would be
> > > https://issues.apache.org/jira/browse/FLINK-1548
> > >
> > > Summary: Be magic in the APIs, be explicit and simple in the runtime.
> > >
> > > Greetings,
> > > Stephan
> > >
> >
>