Greg Hogan created FLINK-2909:
-
Summary: Gelly Graph Generators
Key: FLINK-2909
URL: https://issues.apache.org/jira/browse/FLINK-2909
Project: Flink
Issue Type: New Feature
Components:
Greg Hogan created FLINK-2908:
-
Summary: Web interface redraw web plan when browser resized
Key: FLINK-2908
URL: https://issues.apache.org/jira/browse/FLINK-2908
Project: Flink
Issue Type: Improv
Greg Hogan created FLINK-2907:
-
Summary: Bloom filter for Join
Key: FLINK-2907
URL: https://issues.apache.org/jira/browse/FLINK-2907
Project: Flink
Issue Type: New Feature
Components: J
Hello all,
We are about to finalise following design. Please review it in the google
doc below. And let us know your inputs.
https://docs.google.com/document/d/1SChonW4bXNiqU2Pz9PPjuKDuKrBGmESrPcJXamj4dlI/edit
-- Saumitra S. Shahapure
On Thu, Oct 22, 2015 at 1:00 PM, Saumitra Shahapure <
saumit
Hi everybody,
I created a wiki page for our Pull Request Process. [1]
Please review, refine, and comment.
I would suggest to start following the process once 0.10 is released.
What do you think?
Cheers,
Fabian
[1]
https://cwiki.apache.org/confluence/display/FLINK/Pull+Request+Management
2015-1
Great project. Thanks for sharing!
On Thu, Oct 22, 2015 at 9:29 PM, Ufuk Celebi wrote:
> Wow! Very nice. Thanks for sharing. I will try it out :-)
>
> On Thursday, October 22, 2015, Kunft, Andreas
> wrote:
>
> > FYI:
> >
> >
> > FastR on Flink, a project to combine the R programming language wi
Yes. I think that's a good compromise. Additionally, I vote for a
"deadline" (or "target date") to get those JIRAs done (even if we cannot
enforce it) to not get "trapped" by the lazy approach.
On 10/23/2015 02:12 PM, Fabian Hueske wrote:
> Which basically defaults back to lazily adding JavaDocs (
Which basically defaults back to lazily adding JavaDocs (with some
bookkeeping).
I'd be +1 for that.
2015-10-23 14:09 GMT+02:00 Matthias J. Sax :
> A "deadline" is not really forcible.
>
> However, if we have a JIRA for each module, we can enable JavaDoc
> enforcement when the JIRA is resolved.
A "deadline" is not really forcible.
However, if we have a JIRA for each module, we can enable JavaDoc
enforcement when the JIRA is resolved. And we should discuss the
progress about those tickets regularly (to hopefully find volunteers to
resolve them) and use a special tag for them.
On 10/23/20
And who should be "forced" to write the docs before the deadline passes?
That's not going to work either, IMO.
2015-10-23 13:13 GMT+02:00 Matthias J. Sax :
> I don't care about line length.
>
> Still prefer whitespaces because it gives aligned indention for line
> break in method calls (remember
+1 ^^
On 23 October 2015 at 13:14, Matthias J. Sax wrote:
> +1 for 1.0
> it's time to "grow up" :)
>
> On 10/23/2015 12:52 PM, Kostas Tzoumas wrote:
> > +1 for 1.0, it's the right time if not a bit overdue in my opinion
> >
> > On Fri, Oct 23, 2015 at 12:06 PM, Fabian Hueske
> wrote:
> >
> >> Y
+1 for 1.0
it's time to "grow up" :)
On 10/23/2015 12:52 PM, Kostas Tzoumas wrote:
> +1 for 1.0, it's the right time if not a bit overdue in my opinion
>
> On Fri, Oct 23, 2015 at 12:06 PM, Fabian Hueske wrote:
>
>> Yes, let's do it
>> +1
>>
>> 2015-10-23 12:00 GMT+02:00 Stephan Ewen :
>>
>>> +
I don't care about line length.
Still prefer whitespaces because it gives aligned indention for line
break in method calls (remember my example) But I would not vote -1 for
keeping tabs either.
About JavaDocs: I agree with Max that lazy adding will not fix the
problem. There should be some enforc
+1 for 1.0, it's the right time if not a bit overdue in my opinion
On Fri, Oct 23, 2015 at 12:06 PM, Fabian Hueske wrote:
> Yes, let's do it
> +1
>
> 2015-10-23 12:00 GMT+02:00 Stephan Ewen :
>
> > +1 for 1.0 :-)
> >
> > On Fri, Oct 23, 2015 at 11:59 AM, Maximilian Michels
> > wrote:
> >
> > >
Yes, let's do it
+1
2015-10-23 12:00 GMT+02:00 Stephan Ewen :
> +1 for 1.0 :-)
>
> On Fri, Oct 23, 2015 at 11:59 AM, Maximilian Michels
> wrote:
>
> > Dear Flink community,
> >
> > We have forked the current release candidate from the master to the
> > release-0.10-rc0 branch. Changes for the ne
+1 for 1.0 :-)
On Fri, Oct 23, 2015 at 11:59 AM, Maximilian Michels wrote:
> Dear Flink community,
>
> We have forked the current release candidate from the master to the
> release-0.10-rc0 branch. Changes for the next release candidate should
> be pushed to the release-0.10 branch. The master n
Dear Flink community,
We have forked the current release candidate from the master to the
release-0.10-rc0 branch. Changes for the next release candidate should
be pushed to the release-0.10 branch. The master needed to be updated
to deploy only one snapshot version to the Maven repository and to
I am with Vasia.
Are spaces so important that we want to effectively wipe out the entire
commit history?
On Fri, Oct 23, 2015 at 11:51 AM, Vasiliki Kalavri <
vasilikikala...@gmail.com> wrote:
> Hey,
>
> sorry I haven't replied so far. I was enjoying the thread tough :P
>
> I'm +1 for 120 line le
Hey,
sorry I haven't replied so far. I was enjoying the thread tough :P
I'm +1 for 120 line length and tabs. I wouldn't voice a -1 for spaces, but
it seems to me like an unnecessary change that would touch every single
Java file and without substantially improving anything.
JavaDocs by-module wi
Enforcing JavaDocs (no, by-file, by-module, global) is another open
question.
Regarding the line length, I am OK with 120 chars.
2015-10-23 11:29 GMT+02:00 Ufuk Celebi :
> I think that we have two open questions now:
>
> 1. Line length
>
> From the discussion so far, I think that no one wants 80
I think that we have two open questions now:
1. Line length
From the discussion so far, I think that no one wants 80 characters line length.
The final decision will be 100 vs. 120 characters. 120 characters is what we
have right now (for most parts), so it is fair to keep it that way, but enfor
Fabian Hueske created FLINK-2906:
Summary: Remove Record-API
Key: FLINK-2906
URL: https://issues.apache.org/jira/browse/FLINK-2906
Project: Flink
Issue Type: Sub-task
Components: Ja
Martin Junghanns created FLINK-2905:
---
Summary: Add intersect method to Graph class
Key: FLINK-2905
URL: https://issues.apache.org/jira/browse/FLINK-2905
Project: Flink
Issue Type: New Featu
I don't think lazily adding comments will work. However, I'm fine with
adding all the checkstyle rules one module at a time (with a jira
issue to keep track of the modules already converted). It's not going
to happen that we lazily add comments because that's the reason why
comments are missing in
24 matches
Mail list logo
