I'm wondering whether we shouldn't first write down Bylaws that reflect
the current state, and then have separate discussions for individual
amendments. My gut feeling is that this discussion will quickly become a
chaotic mess with plenty points being discussed at once.
On 11/07/2019 20:03, Bo
Hi Xuefu,
thanks for having a look at this. I am sure this playground setup will need
to be maintained and will go through revisions, too. So, we would still
need to keep the content of the archive in some repository + the additional
piece of automation to update the archive, when the documentatio
I am fine with a separate repository, was just raising the other option as
a question.
+1 to go ahead
On Fri, Jul 12, 2019 at 9:49 AM Konstantin Knauf
wrote:
> Hi Xuefu,
>
> thanks for having a look at this. I am sure this playground setup will need
> to be maintained and will go through revisi
Congrats, Rong!
Hequn Cheng 于2019年7月12日周五 下午1:09写道：
> Congratulations Rong!
>
> Best, Hequn
>
> On Fri, Jul 12, 2019 at 12:19 PM Jeff Zhang wrote:
>
>> Congrats, Rong!
>>
>>
>> vino yang 于2019年7月12日周五 上午10:08写道：
>>
>>> congratulations Rong Rong!
>>>
>>> Fabian Hueske 于2019年7月11日周四 下午10:25写道：
vinoyang created FLINK-13240:
Summary: Wrong check argument error message in the constructor of
QueryableStateConfiguration
Key: FLINK-13240
URL: https://issues.apache.org/jira/browse/FLINK-13240
Project:
Hi,
Thanks for the proposal. Generally speaking +1 from my side to the general idea
and most of the content. I also see merit to the Chesney's proposal to start
from the current state. I think either would be fine for me.
Couple of comments:
1.
I also think that requiring +1 from another com
Congratulations Rong!
Best,
Congxian
Biao Liu 于2019年7月12日周五 下午4:40写道：
> Congrats, Rong!
>
>
> Hequn Cheng 于2019年7月12日周五 下午1:09写道：
>
>> Congratulations Rong!
>>
>> Best, Hequn
>>
>> On Fri, Jul 12, 2019 at 12:19 PM Jeff Zhang wrote:
>>
>>> Congrats, Rong!
>>>
>>>
>>> vino yang 于2019年7月12日周五 上
Hi Chesnay,
We could do that. This might actually help unblock other things such as
META-FLIP discussion quicker. Will you or someone familiar enough with the
current state to write it down?
If we are going to have an itemized discussion, I think the parts need
immediate attention are:
1. Vote typ
@Piotr regarding the 3 days voting on the FLIP. This is just about the voting,
before that there needs to be the discussion thread. If three days have passed
on a vote and there is consensus (i.e. 3 committers/PMCs have voted +1) that
seems a high enough bar for me. So far, we have rarely see an
Great work!
> On Jul 12, 2019, at 2:58 PM, Hequn Cheng wrote:
>
> Hi Kurt,
>
> Great work and thanks for the update.
>
> FYI, I find a bug[1] on Table API accidentally. The PR has already been
> opened. I think it would be good if the fix can be included in the 1.9.
>
> Best,
> Hequn
>
> [1]
Zhu Zhu created FLINK-13241:
---
Summary: YarnResourceManager gives no response to second round
slot allocations
Key: FLINK-13241
URL: https://issues.apache.org/jira/browse/FLINK-13241
Project: Flink
Chesnay Schepler created FLINK-13242:
Summary: StandaloneResourceManagerTest fails on travis
Key: FLINK-13242
URL: https://issues.apache.org/jira/browse/FLINK-13242
Project: Flink
Issue T
Hi everyone,
thanks everyone for you remarks and questions! We have three +1s, so I
think, we can proceed with this.
@Robert: Could you create the request to the INFRA?
Thanks,
Konstantin
On Fri, Jul 12, 2019 at 10:16 AM Stephan Ewen wrote:
> I am fine with a separate repository, was just ra
Chesnay Schepler created FLINK-13243:
Summary: AbstractOperatorRestartTestBase fails on Windows
Key: FLINK-13243
URL: https://issues.apache.org/jira/browse/FLINK-13243
Project: Flink
Issu
I will request the repo now, so that you can continue working on the
documentation (thanks for that again :) )
I actually like Xuefu's idea of making an archive available.
The good thing is that we can get this from any GitHub hosted repository.
For example for Flink, this link let's you download
The repo creation was faster than expected:
https://github.com/apache/flink-playgrounds (it's not even listed here yet:
https://gitbox.apache.org/repos/asf)
On Fri, Jul 12, 2019 at 11:55 AM Robert Metzger wrote:
> I will request the repo now, so that you can continue working on the
> documentat
Thanks Robert. I will prepare the first PR early next week.
On Fri, Jul 12, 2019 at 11:58 AM Robert Metzger wrote:
> The repo creation was faster than expected:
> https://github.com/apache/flink-playgrounds (it's not even listed here
> yet:
> https://gitbox.apache.org/repos/asf)
>
>
> On Fri, Ju
Mridul Verma created FLINK-13244:
Summary: Delayed Scheduler in Flink
Key: FLINK-13244
URL: https://issues.apache.org/jira/browse/FLINK-13244
Project: Flink
Issue Type: Improvement
Wouldn't this qualify for releasing snapshot artifacts to users? (Which,
you know, shouldn't be done?)
On 12/07/2019 11:55, Robert Metzger wrote:
I will request the repo now, so that you can continue working on the
documentation (thanks for that again :) )
I actually like Xuefu's idea of maki
That's a good point. We should point readers in the documentation to the
repository first, and then write "for convenience, you can also download a
snapshot of the repository here" AND put a disclaimer on the page, that
this archive is not an official product released by the Flink PMC.
Since this
Chesnay Schepler created FLINK-13245:
Summary: Network stack is leaking files
Key: FLINK-13245
URL: https://issues.apache.org/jira/browse/FLINK-13245
Project: Flink
Issue Type: Bug
The last time this came up was about our download page which contained
snapshot links, with a big warning that these are for dev purposes, and
we had to take that down. Back than the conclusion was that snapshot
artifacts must only be linked on pages intended for developers, and most
not be vis
MalcolmSanders created FLINK-13246:
--
Summary: Implement external shuffle service for Kubernetes
Key: FLINK-13246
URL: https://issues.apache.org/jira/browse/FLINK-13246
Project: Flink
Issue T
MalcolmSanders created FLINK-13247:
--
Summary: Implement external shuffle service for YARN
Key: FLINK-13247
URL: https://issues.apache.org/jira/browse/FLINK-13247
Project: Flink
Issue Type: N
Hi Aljoscha and Becket
Right, 3 days for FLIP voting is fine I think.
>> I’m missing this stated somewhere clearly. If we are stating that a single
>> committers +1 is good enough for code review, with 0 hours delay (de facto
>> the current state), we should also write down that this is subject t
Hi Chesnay,
thanks for joining the discussion. For clarification: the repository will
only contain a docker-compose.yaml and a few configuration files. In terms
of Flink images the plan is to use `library/flink:`
[1].
Best,
Konstantin
[1] https://github.com/docker-flink/docker-flink
On Fri, Ju
Stefan Richter created FLINK-13248:
--
Summary: Enhance mailbox executor with yield-to-downstream
functionality
Key: FLINK-13248
URL: https://issues.apache.org/jira/browse/FLINK-13248
Project: Flink
vg
On Fri 12 Jul, 2019, 7:19 PM Stefan Richter (JIRA), wrote:
> Stefan Richter created FLINK-13248:
> --
>
> Summary: Enhance mailbox executor with yield-to-downstream
> functionality
> Key: FLINK-13248
> URL: htt
Till Rohrmann created FLINK-13249:
-
Summary: Distributed Jepsen test fails with blocked TaskExecutor
Key: FLINK-13249
URL: https://issues.apache.org/jira/browse/FLINK-13249
Project: Flink
Iss
Stephan Ewen created FLINK-13250:
Summary: Blink Planner should assign concrete resources to all
nodes
Key: FLINK-13250
URL: https://issues.apache.org/jira/browse/FLINK-13250
Project: Flink
Hi,
Sorry for the quite late response!
I initially understood FLIP-45 [0] more as a “allow user to
stop-with-checkpoint”, that’s why I didn’t think too much about the other
things it mentions like semantics of savepoints and checkpoints. I thought that
the “stop-with-checkpoint” would work ver
Hi Caizhi,
from my understanding, the "ProjectableTableSource" interface is used for
something like predicator push-down scenarios:
where your produced output should be the same as how your SELECT statement
requires.
For example, in the case of:
SourceSchema: {a: Int, b: Double, c: String, d: Lon
Hi All,
I just found our flink benchmark Jenkins build [1] is broken with below
error:
*[ERROR] Failed to execute goal on project flink-hackathon-benchmarks:
Could not resolve dependencies for project
org.apache.flink.benchmark:flink-hackathon-benchmarks:jar:0.1: Failure to
find org.apache.flink:
Yu Li created FLINK-13251:
-
Summary: Add bandwidth throttling for checkpoint
uploading/downloading
Key: FLINK-13251
URL: https://issues.apache.org/jira/browse/FLINK-13251
Project: Flink
Issue Type:
Hello all,
on Thursday i pushed an update to the CiBot so that it
* only maintains a single comment, updating it for each new build
* also links in-progress/queued builds, instead of just finished ones.
The update also included a bug that causes the bot to not recognize
which commits have be
* only maintains a single comment, updating it for each new build
* also links in-progress/queued builds, instead of just finished ones.
Want to clarify that the above changes still hold?
On Fri, Jul 12, 2019 at 3:56 PM Chesnay Schepler wrote:
> Hello all,
>
> on Thursday i pushed an upda
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is kangzai my full name is likang
Hi Rong,
Thanks for your explanation. What I'm wondering when implementing this
interface is that, will `projectFields` be called twice in a row?
(something like `source.projectFields().projectFields()`) For example if
user writes "select c, d from (select a, c, d from my_table)". In this case
we
Yes.
On 13/07/2019 01:56, Bowen Li wrote:
* only maintains a single comment, updating it for each new build
* also links in-progress/queued builds, instead of just finished ones.
Want to clarify that the above changes still hold?
On Fri, Jul 12, 2019 at 3:56 PM Chesnay Schepler wrote:
39 matches
Mail list logo
