Travis replied me with very good news: Somebody from INFRA was asking the
same question around the same time as I did and Travis is working on adding
more build capacity for the "apache" github organization.
I hope we'll soon have quicker builds again.
On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputr
Great!
Thanks Robert for sharing the good news :-)
2015-03-26 9:08 GMT+01:00 Robert Metzger :
> Travis replied me with very good news: Somebody from INFRA was asking the
> same question around the same time as I did and Travis is working on adding
> more build capacity for the "apache" github org
+Table API
Same thoughts as Stephan. Table is more common in the economy than Relation.
On 25.03.2015 21:30, Stephan Ewen wrote:
+Table API / Table
I have a feeling that Relation is a name mostly used by people with a
deeper background in (relational) databases, while table is more the
pragmat
+Table
I also agree with that line of argument (think SQL ;-) )
-Ursprüngliche Nachricht-
Von: Timo Walther [mailto:twal...@apache.org]
Gesendet: Donnerstag, 26. März 2015 09:28
An: dev@flink.apache.org
Betreff: Re: [VOTE] Name of Expression API Representation
+Table API
Same thoughts
+DataTable
On Thu, Mar 26, 2015 at 9:29 AM, Markl, Volker, Prof. Dr. <
volker.ma...@tu-berlin.de> wrote:
> +Table
>
> I also agree with that line of argument (think SQL ;-) )
>
> -Ursprüngliche Nachricht-
> Von: Timo Walther [mailto:twal...@apache.org]
> Gesendet: Donnerstag, 26. März 201
+Table
On Thu, Mar 26, 2015 at 9:32 AM, Márton Balassi
wrote:
> +DataTable
>
> On Thu, Mar 26, 2015 at 9:29 AM, Markl, Volker, Prof. Dr. <
> volker.ma...@tu-berlin.de> wrote:
>
> > +Table
> >
> > I also agree with that line of argument (think SQL ;-) )
> >
> > -Ursprüngliche Nachricht-
>
Thanks Henry. :D
+Relation
On Thu, Mar 26, 2015 at 9:36 AM, Till Rohrmann wrote:
> +Table
>
> On Thu, Mar 26, 2015 at 9:32 AM, Márton Balassi
> wrote:
>
>> +DataTable
>>
>> On Thu, Mar 26, 2015 at 9:29 AM, Markl, Volker, Prof. Dr. <
>> volker.ma...@tu-berlin.de> wrote:
>>
>> > +Table
>> >
>> >
+Table
On Thu, Mar 26, 2015 at 10:13 AM, Aljoscha Krettek
wrote:
> Thanks Henry. :D
>
> +Relation
>
> On Thu, Mar 26, 2015 at 9:36 AM, Till Rohrmann
> wrote:
> > +Table
> >
> > On Thu, Mar 26, 2015 at 9:32 AM, Márton Balassi <
> balassi.mar...@gmail.com>
> > wrote:
> >
> >> +DataTable
> >>
> >
Ufuk Celebi created FLINK-1786:
--
Summary: Add support for pipelined programs with slot count
exceeding parallelism
Key: FLINK-1786
URL: https://issues.apache.org/jira/browse/FLINK-1786
Project: Flink
I suspect this error only happens once in a while. We didn't change
anything on these tests recently.
Your PR for fixing this issue looks good, maybe its fixing it.
On Thu, Mar 26, 2015 at 3:15 AM, Henry Saputra
wrote:
> Hi All,
>
> I just pulled from master and seemed like it fails mvn test:
>
I created a "starter" task JIRA for this.
https://issues.apache.org/jira/browse/FLINK-1787
On Sun, Mar 8, 2015 at 3:23 PM, Aljoscha Krettek
wrote:
> +1 I also tend to use guava.
>
> On Sun, Mar 8, 2015 at 3:21 PM, Ufuk Celebi wrote:
> >
> > On 08 Mar 2015, at 15:05, Stephan Ewen wrote:
> >
>
Robert Metzger created FLINK-1787:
-
Summary: Remove commons Validate calls with Guava checkArgument()
calls.
Key: FLINK-1787
URL: https://issues.apache.org/jira/browse/FLINK-1787
Project: Flink
Two weeks have passed since we've discussed the 0.9 release the last time.
The ApacheCon is in 18 days from now.
If we want, we can also release a "0.9.0-beta" release that contains known
bugs, but allows our users to try out the new features easily (because they
are part of a release). The vote f
I didn't know that there was already an issue for this. I closed FLINK-1787.
The correct issue is this one:
https://issues.apache.org/jira/browse/FLINK-1711
That's nice to hear. They didn't specify any time frame?
On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske wrote:
> Great!
> Thanks Robert for sharing the good news :-)
>
> 2015-03-26 9:08 GMT+01:00 Robert Metzger :
>
> > Travis replied me with very good news: Somebody from INFRA was asking the
> >
No, but we can ask David Nalley from Infra, he is talking to them.
On Thu, Mar 26, 2015 at 11:13 AM, Maximilian Michels wrote:
> That's nice to hear. They didn't specify any time frame?
>
> On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske wrote:
>
> > Great!
> > Thanks Robert for sharing the good
+1 for an early milestone release. Perhaps we can call it 0.9-milestone or
so?
On Thu, Mar 26, 2015 at 11:01 AM, Robert Metzger
wrote:
> Two weeks have passed since we've discussed the 0.9 release the last time.
>
> The ApacheCon is in 18 days from now.
> If we want, we can also release a "0.9.0
Yes, please. Would be interesting to know approximately when they implement
to extend the capacity for Apache repositories and how large it is going to
be.
On Thu, Mar 26, 2015 at 11:14 AM, Robert Metzger
wrote:
> No, but we can ask David Nalley from Infra, he is talking to them.
>
> On Thu, Mar
+1 for an early release. It will help unblock the samoa PR that has 0.9
dependencies.
> On 26 Mar 2015, at 11:44, Kostas Tzoumas wrote:
>
> +1 for an early milestone release. Perhaps we can call it 0.9-milestone or
> so?
>
> On Thu, Mar 26, 2015 at 11:01 AM, Robert Metzger
> wrote:
>
>> Two
+Table
2015-03-26 10:28 GMT+01:00 Robert Metzger :
> +Table
>
>
> On Thu, Mar 26, 2015 at 10:13 AM, Aljoscha Krettek
> wrote:
>
> > Thanks Henry. :D
> >
> > +Relation
> >
> > On Thu, Mar 26, 2015 at 9:36 AM, Till Rohrmann
> > wrote:
> > > +Table
> > >
> > > On Thu, Mar 26, 2015 at 9:32 AM, Márt
+Table
On Thursday, March 26, 2015, Alexander Alexandrov <
alexander.s.alexand...@gmail.com> wrote:
> +Table
>
> 2015-03-26 10:28 GMT+01:00 Robert Metzger >:
>
> > +Table
> >
> >
> > On Thu, Mar 26, 2015 at 10:13 AM, Aljoscha Krettek >
> > wrote:
> >
> > > Thanks Henry. :D
> > >
> > > +Relation
Hi Stephan,
Yes, you are right. I will try writing a custom data source as you
mentioned. Also, I still need to check the possibility of our system to use
Apache Kafka as a broker. Could it be possible for you to point out here
the downsides of using UDP as a source for streaming data?
Thanks,
Ja
+Table
发件人: aalexandrov [via Apache Flink (Incubator) Mailing List archive.]
[mailto:ml-node+s1008284n4743...@n3.nabble.com]
发送时间: 2015年3月26日 19:40
收件人: Hongsibao
主题: Re: [VOTE] Name of Expression API Representation
+Table
2015-03-26 10:28 GMT+01:00 Robert Metzger <[hidden
email]>:
> +Table
>
+1 for a beta release: 0.9-beta.
On Thu, Mar 26, 2015 at 12:09 PM, Paris Carbone wrote:
> +1 for an early release. It will help unblock the samoa PR that has 0.9
> dependencies.
>
> > On 26 Mar 2015, at 11:44, Kostas Tzoumas wrote:
> >
> > +1 for an early milestone release. Perhaps we can call
Dear Janani,
Apache Kafka as a source is supported by our system, check out the
documentation for details. [1]
You can use UDP as a source if you wish, just bear in mind the standard
disadvantages of it: the possibility of losing messages and that you will
have to manually deal with the serializa
Aljoscha Krettek created FLINK-1788:
---
Summary: Extend Table API to allow logical plan optimisations
Key: FLINK-1788
URL: https://issues.apache.org/jira/browse/FLINK-1788
Project: Flink
Issu
+1 for the early release.
I'd call it 0.9-milestone1.
On Thu, Mar 26, 2015 at 1:37 PM, Maximilian Michels wrote:
> +1 for a beta release: 0.9-beta.
>
> On Thu, Mar 26, 2015 at 12:09 PM, Paris Carbone wrote:
>
> > +1 for an early release. It will help unblock the samoa PR that has 0.9
> > depen
+1 for a beta release. So there is no feature-freeze until the RC right?
On 26.03.2015 15:32, Márton Balassi wrote:
+1 for the early release.
I'd call it 0.9-milestone1.
On Thu, Mar 26, 2015 at 1:37 PM, Maximilian Michels wrote:
+1 for a beta release: 0.9-beta.
On Thu, Mar 26, 2015 at 12:
@Timo: No feature freeze for this, yes.
On Thu, Mar 26, 2015 at 3:36 PM, Timo Walther wrote:
> +1 for a beta release. So there is no feature-freeze until the RC right?
>
>
>
> On 26.03.2015 15:32, Márton Balassi wrote:
>
>> +1 for the early release.
>>
>> I'd call it 0.9-milestone1.
>>
>> On Thu
On 26 Mar 2015, at 11:01, Robert Metzger wrote:
> Two weeks have passed since we've discussed the 0.9 release the last time.
>
> The ApacheCon is in 18 days from now.
> If we want, we can also release a "0.9.0-beta" release that contains known
> bugs, but allows our users to try out the new fea
Looks like we need to vote on 0.9-beta or 0.9-milestone.
Can we find consensus whether to add a 1 after the name? -beta1 or
-milestone1.
Adding a 1 allows us to create a second beta/milestone release.
I'm against adding a 1.
On Thu, Mar 26, 2015 at 3:40 PM, Ufuk Celebi wrote:
>
> On 26 Mar 201
Timo Walther created FLINK-1789:
---
Summary: Allow adding of URLs to the usercode class loader
Key: FLINK-1789
URL: https://issues.apache.org/jira/browse/FLINK-1789
Project: Flink
Issue Type: Imp
Awesome news!
On Thursday, March 26, 2015, Robert Metzger wrote:
> Travis replied me with very good news: Somebody from INFRA was asking the
> same question around the same time as I did and Travis is working on adding
> more build capacity for the "apache" github organization.
> I hope we'll so
I think it looks good for a start, we will have to work on the API a little
bit together to make it fit smoothly with what we currently have.
There is a few gaps in the timeline but that you have probably noticed :)
Otherwise +1 from me.
On Wed, Mar 25, 2015 at 11:35 PM, Akshay Dixit wrote:
>
If we wanted to, we could still release a -milestone2 even with a
-milestone.
On Thu, Mar 26, 2015 at 3:44 PM, Robert Metzger wrote:
> Looks like we need to vote on 0.9-beta or 0.9-milestone.
>
> Can we find consensus whether to add a 1 after the name? -beta1 or
> -milestone1.
> Adding a 1 allow
Hello everyone,
I guess I need to revive this old discussion:
http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/Memory-segment-error-when-migrating-functional-code-from-Flink-0-9-to-0-8-td3687.html
At that point, the fix was to kindly ask Alex to make his project work with
Hi,
during startup, Flink will log something like:
16:48:09,669 INFO org.apache.flink.runtime.taskmanager.TaskManager
- Using 1193 MB for Flink managed memory.
Can you tell us how much memory Flink is managing in your case?
On Thu, Mar 26, 2015 at 4:46 PM, Andra Lungu wrote:
> Hello ev
Sibao Hong created FLINK-1790:
-
Summary: Remove the redunant import code
Key: FLINK-1790
URL: https://issues.apache.org/jira/browse/FLINK-1790
Project: Flink
Issue Type: Improvement
Com
Aljoscha Krettek created FLINK-1791:
---
Summary: Change nightly Javadoc build to use correct profile
Key: FLINK-1791
URL: https://issues.apache.org/jira/browse/FLINK-1791
Project: Flink
Issue
I think "Milestone" pretty much says that we have some crucial things in
there, but not all. "Beta" in comparison, has an "immature early version"
connotation.
We are, for example, using a milestone 1 version of Jetty for the Web
Frontend, so that is a pretty standard thing, in my opinion:
org.e
I think you meant Fabian ;-)
On Wed, Mar 25, 2015 at 4:05 PM, Henry Saputra
wrote:
> Hi Stephan,
>
> Glad to meet and chat for sure =)
>
> Love to see Flink represented in the ApacheCon.
>
> - Henry
>
> On Wed, Mar 25, 2015 at 3:12 AM, Fabian Hueske wrote:
> > Thanks Henry for sharing!
> >
> >
Oh my goodness, I am so sorry Fabian =(
I sent the email out in the morning before I hit my coffee.
Looking forward meeting you at the ApacheCon, Fabian =)
- Henry
On Thu, Mar 26, 2015 at 10:26 AM, Stephan Ewen wrote:
> I think you meant Fabian ;-)
>
> On Wed, Mar 25, 2015 at 4:05 PM, Henry Sa
The ASF press team wants to announce next week, so a 3-day vote right now
might cancel the subject line of this thread :-)
Perhaps we can reach consensus in the DISCUSS thread or have a 24-hour vote?
I agree with Stephan on 0.9.0.M1 (or 0.9.0-m1 or whatever), as it seems
that other open source pr
I'm fine with milestone.
But I would really like to call it "milestone" instead of "M1" .. because I
actually never though about that weird version name of Jetty ... I fear
that our users would also be confused by this.
On Thu, Mar 26, 2015 at 7:03 PM, Kostas Tzoumas wrote:
> The ASF press team
Hello,
I will be applying to the Google Summer of Code, and I wrote most of
the proposal:
http://compalg.inf.elte.hu/~ggevay/Proposal.pdf
I would appreciate it if you could comment on it.
Gyula Fora, git blame is telling me that you wrote most of the
relevant parts of the windowing code, so I wou
Thanks for going through it Gyula.
I've made the necessary amends to the timeline and submitted the proposal.
Regards,
Akshay Dixit
On Thu, Mar 26, 2015 at 8:53 PM, Gyula Fóra wrote:
> I think it looks good for a start, we will have to work on the API a little
> bit together to make it fit smo
On Thursday, March 26, 2015, Robert Metzger wrote:
> I'm fine with milestone.
> But I would really like to call it "milestone" instead of "M1" .. because I
> actually never though about that weird version name of Jetty ... I fear
> that our users would also be confused by this.
Same here.
Yeah, always prefer to get it with consensus that VOTE
I am fine with either.
- Henry
On Thu, Mar 26, 2015 at 11:03 AM, Kostas Tzoumas wrote:
> The ASF press team wants to announce next week, so a 3-day vote right now
> might cancel the subject line of this thread :-)
>
> Perhaps we can reach c
Hey Gabor,
Thank you for the proposal. It has many interesting ideas and a good
potential.
My comments:
We already have a large amount of ongoing work on the windowing
optimizations, covering your suggestions in section 1. It would be better
to drop that part from the project because thats very
Sure,
3470 [main] INFO org.apache.flink.runtime.taskmanager.TaskManager - Using
820 MB for Flink managed memory.
On Thu, Mar 26, 2015 at 4:48 PM, Robert Metzger wrote:
> Hi,
>
> during startup, Flink will log something like:
> 16:48:09,669 INFO org.apache.flink.runtime.taskmanager.TaskManage
For 20 edges and 5 nodes, that should be more thank enough.
On Thu, Mar 26, 2015 at 11:24 PM, Andra Lungu wrote:
> Sure,
>
> 3470 [main] INFO org.apache.flink.runtime.taskmanager.TaskManager -
> Using 820 MB for Flink managed memory.
>
> On Thu, Mar 26, 2015 at 4:48 PM, Robert Metzger
> wrote
Hi Gabor,
Approximate statistics is a really good topic, I think there is a lot to do if
you focus there. One idea would also be to include some of your contributions
to the incremental machine learning library that will be available by June.
From there you will be able to also use sampling and
Hi Andra,
the error is independent of the size of the data set. A HashTable needs at
least 33 memory pages to operate.
Since you have 820MB of managed memory and the size of a memory page is
32KB, there should be more than 25k pages available.
Can you post the execution plan of the program you ex
Hi Fabian,
I uploaded a file with my execution plan.
On Thu, Mar 26, 2015 at 11:50 PM, Fabian Hueske wrote:
> Hi Andra,
>
> the error is independent of the size of the data set. A HashTable needs at
> least 33 memory pages to operate.
> Since you have 820MB of managed memory and the size of a m
Opps! Sorry! Did not know the mailing list does not support attachments :)
https://gist.github.com/andralungu/fba36d77f79189daa183
On Fri, Mar 27, 2015 at 12:02 AM, Andra Lungu wrote:
> Hi Fabian,
>
> I uploaded a file with my execution plan.
>
> On Thu, Mar 26, 2015 at 11:50 PM, Fabian Hueske
Hello,
Thank you very much for your comments! I will remove the part about
the windowing optimizations (though, that was my favourite part :) ),
and think about what other statistics could be added. And thank you
for the link with the collection of many relevant algorithms, they are
very interesti
56 matches
Mail list logo
