+1
On Tue, Feb 17, 2015 at 2:40 PM, Aljoscha Krettek wrote:
> +1
>
> On Tue, Feb 17, 2015 at 1:34 PM, Till Rohrmann wrote:
>> +1
>>
>> On Tue, Feb 17, 2015 at 1:34 PM, Kostas Tzoumas wrote:
>>
>>> +1
>>>
>>> On Tue, Feb 17, 2015 at 12:14 PM, Márton Balassi
>>> wrote:
>>>
>>> > When it comes to
Ufuk Celebi created FLINK-1577:
--
Summary: Misleading error messages when cancelling tasks
Key: FLINK-1577
URL: https://issues.apache.org/jira/browse/FLINK-1577
Project: Flink
Issue Type: Improve
Stephan Ewen created FLINK-1578:
---
Summary: Overhaul BLOB manager
Key: FLINK-1578
URL: https://issues.apache.org/jira/browse/FLINK-1578
Project: Flink
Issue Type: Bug
Components: JobMa
Moved this to the Wiki:
https://cwiki.apache.org/confluence/display/FLINK/Coding+Guidelines+for+Scala
On Mon, Feb 16, 2015 at 4:29 PM, Paris Carbone wrote:
> +1
>
> Good point. In general, keeping the common/runtime as simple as possible
> is quite important
>
> > On 16 Feb 2015, at 16:05, Till
+1
I agree it’s a proper way to go.
On 18 Feb 2015, at 10:41, Max Michels mailto:m...@apache.org>>
wrote:
+1
On Tue, Feb 17, 2015 at 2:40 PM, Aljoscha Krettek
mailto:aljos...@apache.org>> wrote:
+1
On Tue, Feb 17, 2015 at 1:34 PM, Till Rohrmann
mailto:trohrm...@apache.org>> wrote:
+1
On Tu
Dear Flinker,
can anyone try to build a Flink program against the 0.9-SNAPSHOT?
I receive the following maven error
[ERROR] error: error while loading , invalid CEN header (bad
signature)
[ERROR] error: scala.reflect.internal.MissingRequirementError: object
scala.runtime in compiler mirror not fo
Hi,
do you mean the maven snapshot repository or the nightly build?
On Wed, Feb 18, 2015 at 1:14 PM, Arvid Heise wrote:
> Dear Flinker,
>
> can anyone try to build a Flink program against the 0.9-SNAPSHOT?
>
> I receive the following maven error
> [ERROR] error: error while loading , invalid CE
I mean the snapshots obtained from
https://repository.apache.org/content/repositories/snapshots/
On Wed, Feb 18, 2015 at 1:26 PM, Robert Metzger wrote:
> Hi,
>
> do you mean the maven snapshot repository or the nightly build?
>
> On Wed, Feb 18, 2015 at 1:14 PM, Arvid Heise
> wrote:
>
> > Dear
I just saw that eclipse gives even better hints.
Archive for required library:
'C:/Users/heisea/.m2/repository/org/apache/flink/flink-java/0.9-SNAPSHOT/flink-java-0.9-SNAPSHOT.jar'
in project 'de.bund.bfr.flink.outbreakanalysis' cannot be read or is not a
valid ZIP file
On Wed, Feb 18, 2015 at 1:
Cool. Thank you.
Did the issue persist for a longer period of time? Maybe the upload of the
last snapshot failed.
Stephan pushed to master a few minutes ago (This is the travis build:
https://travis-ci.org/apache/flink/builds/51216823).
Travis will update the snapshot, lets hope that fixes the iss
It is true, you can write endless chains of functions in Scala that become
hard to read, which should be prevented.
In my opinion, line length limits are not a good tool to do that. In most
cases they simply introduce linebreaks between constant names and parameters
which hurt code readability mor
Robert Metzger created FLINK-1579:
-
Summary: Create a Flink History Server
Key: FLINK-1579
URL: https://issues.apache.org/jira/browse/FLINK-1579
Project: Flink
Issue Type: New Feature
Aff
I'm also in favor of shading commonly used libraries to resolve this issue
for our upstream users.
I recently wrote this distributed TPC-H datagenerator, which had a hard
dependency on a newer guava version. So I needed to shade guava in my
project to make it work.
Another candidate to shade is th
I would argue it is helpful especially if you use text editor like vim or
even GitHub diff page.
Most modern scala projects like spark and kafka also enforce the rule.
- Henry
On Wednesday, February 18, 2015, Stephan Ewen wrote:
> It is true, you can write endless chains of functions in Scala
Ah seemed like kafka has taken out the max line rule.
I prefer to keep the max char lines, maybe making it larger than 100,
especially with Scala code.
On Wednesday, February 18, 2015, Henry Saputra
wrote:
> I would argue it is helpful especially if you use text editor like vim or
> even GitHub
+1
We used to have this a couple of releases ago.
On Wed, Feb 18, 2015 at 4:30 PM, Henry Saputra
wrote:
> Hi All,
>
> I am thinking of pushing latest doc in master ((i.e the snapshot
> build) to Flink website to help people follow the latest change and
> development without manually build the d
Hi All,
I am thinking of pushing latest doc in master ((i.e the snapshot
build) to Flink website to help people follow the latest change and
development without manually build the doc.
I think some projects like Apache Tajo, Apache Twill, and AmpLab
Tachyon have this and so far I have seen it is
Thats indeed a great idea and we had support for that.
We also have already the infrastructure to do it in place, I just had not
enough time to figure out how ASF's buildbot works. (I know how it should
work theoretically but I haven't tried it)
This is the respective JIRA:
https://issues.apache.o
This is a must-have. I would like to take a look at the automatic doc
build infrastructure next week. Basically we have to write some
buildbot rules which issue a build and upload of the docs on a daily
basis.
On Wed, Feb 18, 2015 at 4:53 PM, Robert Metzger wrote:
> Thats indeed a great idea and
+1
The website should have the latest stable docs and the latest snapshot
docs. The snapshot docs need not be daily up to date for a start.
On Wed, Feb 18, 2015 at 4:34 PM, Márton Balassi
wrote:
> +1
>
> We used to have this a couple of releases ago.
>
> On Wed, Feb 18, 2015 at 4:30 PM, Henry S
I don't want to remove the rule to encourage people to write ugly scala
code ;)
Also, I hope its the exception to use more than 100 chars.
But there are some cases where it is really okay to have longer lines (for
example exception messages or method signatures in some cases).
I agree with Stephan
We could help this by having shorter local and input argument names and
better timing for the line wrapping.
We already have separate code style for java, for example keeping tabs
instead of spaces, and scala because java code more verbose and declarative
compare to scala.
I am ok with Java do not
Till Rohrmann created FLINK-1580:
Summary: Cleanup TaskManager initialization logic
Key: FLINK-1580
URL: https://issues.apache.org/jira/browse/FLINK-1580
Project: Flink
Issue Type: Bug
Till Rohrmann created FLINK-1581:
Summary: Configure DeathWatch parameters properly
Key: FLINK-1581
URL: https://issues.apache.org/jira/browse/FLINK-1581
Project: Flink
Issue Type: Bug
Márton Balassi created FLINK-1582:
-
Summary: SocketStream gets stuck when socket closes
Key: FLINK-1582
URL: https://issues.apache.org/jira/browse/FLINK-1582
Project: Flink
Issue Type: Bug
Till Rohrmann created FLINK-1583:
Summary: TaskManager reregistration in case of a restart
Key: FLINK-1583
URL: https://issues.apache.org/jira/browse/FLINK-1583
Project: Flink
Issue Type: Bug
Signature source file looks good
Checksum source file looks good
LICENSE file looks good
NOTICE file looks good
README looks good
No 3rd part executable
Compiled and run tests
+1
- Henry
On Mon, Feb 16, 2015 at 6:54 AM, Robert Metzger wrote:
> Please vote on releasing the following candidate
27 matches
Mail list logo
