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:
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:
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
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
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 rmetz...@apache.org wrote:
Thats
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
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 par...@kth.se wrote:
+1
Good point. In general, keeping the common/runtime as simple as possible
is quite important
On 16 Feb 2015, at
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
+1
I agree it’s a proper way to go.
On 18 Feb 2015, at 10:41, Max Michels m...@apache.orgmailto:m...@apache.org
wrote:
+1
On Tue, Feb 17, 2015 at 2:40 PM, Aljoscha Krettek
aljos...@apache.orgmailto:aljos...@apache.org wrote:
+1
On Tue, Feb 17, 2015 at 1:34 PM, Till Rohrmann
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
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:
+1
We used to have this a couple of releases ago.
On Wed, Feb 18, 2015 at 4:30 PM, Henry Saputra henry.sapu...@gmail.com
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
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
I mean the snapshots obtained from
https://repository.apache.org/content/repositories/snapshots/
On Wed, Feb 18, 2015 at 1:26 PM, Robert Metzger rmetz...@apache.org wrote:
Hi,
do you mean the maven snapshot repository or the nightly build?
On Wed, Feb 18, 2015 at 1:14 PM, Arvid Heise
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 se...@apache.org wrote:
It is true, you can write endless chains of
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 henry.sapu...@gmail.com
wrote:
I would argue it is helpful especially if you use text editor
16 matches
Mail list logo
