Robert Metzger created FLINK-16373:
--
Summary: EmbeddedLeaderService: IllegalStateException: The RPC
connection is already closed
Key: FLINK-16373
URL: https://issues.apache.org/jira/browse/FLINK-16373
Robert Metzger created FLINK-16370:
--
Summary: YARNHighAvailabilityITCase fails on JDK11 nightly test:
NoSuchMethodError:
org.apache.flink.shaded.zookeeper3.org.apache.zookeeper.server.quorum.flexible.QuorumMaj
Key: FLINK-16370
3D+%22Build+System+%2F+Azure+Pipelines%22>
" component.
On Mon, Feb 17, 2020 at 12:23 PM Robert Metzger wrote:
> @Leonard: On Azure, I'm not splitting the execution of the end to end
> tests anymore. We won't have the overhead of compiling the same profile
> multiple times
Robert Metzger created FLINK-16330:
--
Summary: Set up environment variables for the S3 tests in Azure
Key: FLINK-16330
URL: https://issues.apache.org/jira/browse/FLINK-16330
Project: Flink
Robert Metzger created FLINK-16329:
--
Summary: Set up build notifications from AZP to builds@f.a.o
Key: FLINK-16329
URL: https://issues.apache.org/jira/browse/FLINK-16329
Project: Flink
Robert Metzger created FLINK-16313:
--
Summary: flink-state-processor-api: surefire execution unstable on
Azure
Key: FLINK-16313
URL: https://issues.apache.org/jira/browse/FLINK-16313
Project: Flink
Robert Metzger created FLINK-16292:
--
Summary: Execute all end to end tests on AZP
Key: FLINK-16292
URL: https://issues.apache.org/jira/browse/FLINK-16292
Project: Flink
Issue Type: Sub-task
Robert Metzger created FLINK-16283:
--
Summary: NullPointerException in GroupAggProcessFunction
Key: FLINK-16283
URL: https://issues.apache.org/jira/browse/FLINK-16283
Project: Flink
Issue
Robert Metzger created FLINK-16265:
--
Summary: TPC-H end-to-end test (Blink Planner): Encodings that
differ from the schema are not supported yet for CsvTableSources.
Key: FLINK-16265
URL: https
Robert Metzger created FLINK-16264:
--
Summary: SQLClientKafkaITCase fails with: Could not map the schema
field 'rowtime' to a field from source.
Key: FLINK-16264
URL: https://issues.apache.org/jira/browse/FLINK
Robert Metzger created FLINK-16263:
--
Summary: BaseRowArrowReaderWriterTest/RowArrowReaderWriterTest
sun.misc.Unsafe or java.nio.DirectByteBuffer.(long, int) not available
Key: FLINK-16263
URL: https
Robert Metzger created FLINK-16256:
--
Summary: HiveTableSourceTest / TableEnvHiveConnectorTest are
failing on optimizer plan validation
Key: FLINK-16256
URL: https://issues.apache.org/jira/browse/FLINK-16256
Robert Metzger created FLINK-16228:
--
Summary: test_mesos_wordcount.sh fails
Key: FLINK-16228
URL: https://issues.apache.org/jira/browse/FLINK-16228
Project: Flink
Issue Type: Bug
Robert Metzger created FLINK-16227:
--
Summary: Streaming bucketing end-to-end test /
test_streaming_bucketing.sh unstable
Key: FLINK-16227
URL: https://issues.apache.org/jira/browse/FLINK-16227
; >
> > On 18/02/2020 13:03, Aljoscha Krettek wrote:
> > > Wouldn't removing the ES 2.x connector be enough because we can then
> > > update the ES 5.x connector? It seems there are some users that still
> > > want to use that one.
> > >
> > > Best
ts use
> parts of the hotfix commits, then it makes the cherry-picking more tricky
> and the commits should have the JIRA issue tag. But I would be fine with
> trying it out.
>
> Cheers,
> Till
>
> On Mon, Feb 17, 2020 at 3:56 PM Robert Metzger
> wrote:
>
> > Hi a
Robert Metzger created FLINK-16136:
--
Summary:
YarnPrioritySchedulingITCase.yarnApplication_submissionWithPriority_shouldRespectPriority()
fails
Key: FLINK-16136
URL: https://issues.apache.org/jira/browse/FLINK
The ES5 connector is causing some problems on the CI system. It would be
nice if we could make a decision here soon. I don't want to invest time
into fixing it, if we are going to remove it.
I'm still in favor of removing it. If we see that there's demand for the
5.x connector after the 1.11
Tracking this here: https://issues.apache.org/jira/browse/FLINK-16122
On Sat, Feb 15, 2020 at 8:12 PM Robert Metzger wrote:
> I agree that we need to fix this.
>
> We could either misuse the "build artifact" feature of azure pipelines to
> publish the logs, or we s
Robert Metzger created FLINK-16122:
--
Summary: build system: transfer.sh uploads are unstable (February
2020)
Key: FLINK-16122
URL: https://issues.apache.org/jira/browse/FLINK-16122
Project: Flink
provided in the commit
> > message?
> >
> > Counting hotfixes by contributor, the top of the list looks as I would
> > expect.
> >
> > Greg
> >
> > Note: this summary is rather naive and includes non-squashed hotfix
> commits
> > included in a
bring up this topic. The 2 ARM machines(16cores) which I
> >> donated is just for POC test. We(Huawei) can donate more once moving to
> >> official Azure pipeline. :)
> >>
> >> Robert Metzger 于2019年12月6日周五 上午3:25写道：
> >>
> >>> Thanks for your
I agree that we need to fix this.
We could either misuse the "build artifact" feature of azure pipelines to
publish the logs, or we set up something simple for Flink (like running an
instance of https://github.com/lachs0r/0x0 or
https://github.com/dutchcoders/transfer.sh :) )
On Fri, Feb 14,
+1 (binding)
- Checked some artifacts in the staging repo
- checked license documentation
- source release is binary free
On Fri, Feb 14, 2020 at 8:01 AM Dian Fu wrote:
> +1 (non-binding)
>
> - Verified the signature and checksum
> - Checked the release note that all the tickets included in
Robert Metzger created FLINK-16018:
--
Summary: Improve error reporting when submitting batch job
(instead of AskTimeoutException)
Key: FLINK-16018
URL: https://issues.apache.org/jira/browse/FLINK-16018
Thanks for starting this discussion!
+1 to drop both
On Mon, Feb 10, 2020 at 2:45 PM Dawid Wysakowicz
wrote:
> Hi all,
>
> As described in this https://issues.apache.org/jira/browse/FLINK-11720
> ticket our elasticsearch 5.x connector does not work out of the box on
> some systems and requires
Robert Metzger created FLINK-15903:
--
Summary: Make REST port configurable in end to end test scripts
Key: FLINK-15903
URL: https://issues.apache.org/jira/browse/FLINK-15903
Project: Flink
Robert Metzger created FLINK-15834:
--
Summary: Set up nightly cron jobs on Azure Pipelines build
Key: FLINK-15834
URL: https://issues.apache.org/jira/browse/FLINK-15834
Project: Flink
Issue
Robert Metzger created FLINK-15833:
--
Summary: Fix 'Kerberized YARN on Docker' e2e test on Azure
Pipelines
Key: FLINK-15833
URL: https://issues.apache.org/jira/browse/FLINK-15833
Project: Flink
Thanks a lot for this work! I believe the web UI is very important, in
particular to new users. I'm very happy to see that you are putting effort
into improving the visibility into Flink through the proposed changes.
I can not judge if all the changes make total sense, but the discussion has
been
ed, Dec 18, 2019 at 5:35 PM Robert Metzger
> wrote:
>
>> I guess we are talking about this profile [1] in the pom.xml?
>>
>> +1 to remove.
>>
>> I'm not sure if we need to rush this for the 1.10 release. The profile is
>> not doing us any harm at the momen
d a ticket if a commiter could please assign it to my
> Jira:
> > sjwiesman
> >
> > https://issues.apache.org/jira/browse/FLINK-15337
> >
> > On Wed, Dec 18, 2019 at 10:29 AM Robert Metzger
> > wrote:
> >
> > > I was actually referring to
Robert Metzger created FLINK-15330:
--
Summary:
org.apache.flink.fs.s3hadoop.HadoopS3RecoverableWriterITCase.testCallingDeleteObjectTwiceDoesNotThroughException()
fails with AssertionError
Key: FLINK-15330
URL
Robert Metzger created FLINK-15327:
--
Summary: 'Walkthrough DataStream Scala nightly' sometimes fails
with InterruptedException
Key: FLINK-15327
URL: https://issues.apache.org/jira/browse/FLINK-15327
I guess we are talking about this profile [1] in the pom.xml?
+1 to remove.
I'm not sure if we need to rush this for the 1.10 release. The profile is
not doing us any harm at the moment.
[1]https://github.com/apache/flink/blob/master/pom.xml#L1035
On Wed, Dec 18, 2019 at 4:51 PM Till Rohrmann
rt, can you elaborate on what you mean by "deployment model"?
> >
> > Seth
> >
> > On Tue, Dec 17, 2019 at 12:19 PM Robert Metzger
> > wrote:
> >
> > > +1 to the general idea
> > >
> > > Maybe we could add "Deployment Mo
+1 to the general idea
Maybe we could add "Deployment Model" in addition to "Supported
Environments" as properties for the vendors.
I'd say Cloudera, Eventador and Huawei [1] are missing from this page
[1]https://www.huaweicloud.com/en-us/product/cs.html
On Tue, Dec 17, 2019 at 5:05 PM Stephan
>> generating an SSL certificate with the distribution.
>>
>> On 12/12/2019 17:45, Robert Metzger wrote:
>> > Hi all,
>> >
>> > There was recently a private report to the Flink PMC, as well as
>> publicly
>> > [1] about Flink's ability to
gt; As for the current split setup we have (as in by modules), it isn't
>> just about faster feedback times; they can also be used to isolate
>> components from each other.
>> > I know that quite a few people appreciate the kafka/python module
>> being in it's own split for exa
I'm generally not opposed to convenience binaries, if a huge number of
people would benefit from them, and the overhead for the Flink project is
low. I did not see a huge demand for such binaries yet (neither for the
Flink + Hive integration). Looking at Apache Spark, they are also only
offering
This discussion has resulted in the following PR:
https://github.com/apache/flink/pull/10559
On Tue, Dec 10, 2019 at 10:14 PM Bowen Li wrote:
> +1 to drop vendor related docs. Links to vendors’ webpages should be enough
>
> On Tue, Dec 10, 2019 at 08:15 Seth Wiesman wrote:
>
> > @uce Agreed.
Hi all,
There was recently a private report to the Flink PMC, as well as publicly
[1] about Flink's ability to execute arbitrary code. In scenarios where
Flink is accessible by somebody unauthorized, this can lead to issues.
The PMC received a similar report in November 2018.
I believe it would
cution
> > in Maven, such that fast projects are executed first. E2E tests should be
> > executed last, which they are somewhat, because of the project
> dependencies.
> >
> > Of course, I'm very interested to improve the overall build experience by
> > explo
Hey devs,
I need your opinion on something: As part of our migration from Travis to
Azure, I'm revisiting the build system of Flink. I currently see two
different ways of proceeding, and I would like to know your opinion on the
two options.
A) We build and test Flink in one "mvn clean verify"
Thanks a lot Seth!
I propose to merge this PR if there's no more feedback within the next 24
hours.
On Mon, Dec 9, 2019 at 6:41 PM Seth Wiesman wrote:
> Hi All!
>
> A while back, Marta opened a PR to create a documentation style guide as
> part of FLIP-42[1][2]. Unfortunately, the review
Robert Metzger created FLINK-15156:
--
Summary: Warn user if System.exit() is called in user code
Key: FLINK-15156
URL: https://issues.apache.org/jira/browse/FLINK-15156
Project: Flink
Issue
ransfer.sh previously.
> I think this feature is also easy to implement in AZP, right?
>
> Best
> Yun Tang
>
> On 12/6/19, 12:19 AM, "Robert Metzger" wrote:
>
> I've created a first draft of my plans in the wiki:
>
> https://cwiki.apache.org/confluen
On Thu, Dec 5, 2019 at 8:46 AM Chesnay Schepler
> wrote:
>
> > Question now is whether the numbers are so low because the docs aren't
> > required or because they are so bad.
> >
> > On 05/12/2019 14:26, Robert Metzger wrote:
> > > I just checked GA:
>
I've created a first draft of my plans in the wiki:
https://cwiki.apache.org/confluence/display/FLINK/%5Bpreview%5D+Azure+Pipelines.
I'm looking forward to your comments.
On Thu, Dec 5, 2019 at 12:37 PM Robert Metzger wrote:
> Thank you all for the positive feedback. I will start putt
I just checked GA:
All numbers are for the last month, independent of the Flink version:
aws.html: 918 pageviews
mapr_setup.html: 108 pageviews
gce_setup.html: 256 pageviews
Some other deployment-related pages for reference:
yarn_setup: 4687
cluster: 4284
kubernetes: 3428
On Thu, Dec 5,
;
> > >>>>>> Just one comment, it's close to 1.10 feature freeze and we will
> > >> spend
> > >>>>>> some
> > >>>>>> time
> > >>>>>> to make tests stable before release. I wish this replacement can
&g
Robert Metzger created FLINK-15056:
--
Summary: Python test:
ExecutionEnvironmentCompletenessTests.test_completeness failed
Key: FLINK-15056
URL: https://issues.apache.org/jira/browse/FLINK-15056
Hi all,
as a follow up from our discussion on reducing the build time [1], I would
like to propose migrating our build infrastructure to Azure Pipelines (away
from Travis).
I believe that we have reached the limits of what Travis can provide the
Flink community, and I don't want the build system
ote:
> >
> > > Hi Robert,
> > > Your proposal skipping FLIP and the vote sounds reasonable to me.
> > >
> > > The project is currently built (with tests, shading, spotbugs etc') in
> > > around 2-3 minutes, but since it will reside in its ow
+1 on removing it.
On Tue, Dec 3, 2019 at 12:31 PM Stephan Ewen wrote:
> I just stumbled across these classes recently and was looking for sample
> uses.
> No examples and other tests in the code base seem to
> use RequiredParameters and OptionType.
>
> They also seem quite redundant with how
I agree that we are only counting PMC votes (because this decision goes
beyond the codebase)
I'm undecided what to vote :) I'm not against setting up a new mailing
list, but I also don't think the benefit (having a private list with PMC +
committers) is enough to justify the work involved. As far
+1 on what has been decided so far in this thread (including using the same
ML, and sticking to the statefun name).
I'm not 100% sure if we need a FLIP for this, as we have VOTEd already with
a 2/3 majority on accepting this contribution, and there are no changes to
the Flink codebase, or
Robert Metzger created FLINK-14856:
--
Summary: Allow setting "state.checkpoints.num-retained" for
individual jobs
Key: FLINK-14856
URL: https://issues.apache.org/jira/browse/FLINK-14856
gt;> oy...@motaword.com
>>
>> <https://www.motaword.com/blog>
>>
>>
>> On Mon, Nov 18, 2019 at 11:07 AM Robert Metzger
>> wrote:
>>
>>> Hi all,
>>>
>>> I would like to announce that Ververica, with the permission
Hi all,
I would like to announce that Ververica, with the permission of the Flink
PMC, is launching a website called flink-packages.org. This goes back to an
effort proposed earlier in 2019 [1]
The idea of the site is to help developers building extensions / connectors
/ API etc. for Flink to get
have the full
> access to the ARM resources as well.
>
> Thanks.
>
> [1 ]
>
> https://docs.microsoft.com/zh-cn/azure/devops/pipelines/agents/v2-linux?view=azure-devops
>
> Robert Metzger 于2019年9月5日周四 下午8:54写道：
>
> > I do have a working Azure setup, yes. E2E test
Hey Xiyuan,
thanks a lot for checking out Travis ARM-based offering.
As part of the "Reducing build times" discussion, we have considered moving
away from Travis to Azure Pipelines. What I want to say is that Travis
might not be important for the Flink community in the long run.
I think running
+1 (binding)
On Mon, Oct 21, 2019 at 12:06 PM Stephan Ewen wrote:
> This is the official vote whether to accept the Stateful Functions code
> contribution to Apache Flink.
>
> The current Stateful Functions code, documentation, and website can be
> found here:
> https://statefun.io/
>
+1 for separate repositories.
This is also good for the community to collect some experience for a
potential repository split effort at some later point.
On Wed, Oct 16, 2019 at 12:01 PM vino yang wrote:
> Hi,
>
> Fast release cycles seems a good viewpoint to support keeping it in a
> separate
Robert Metzger created FLINK-13978:
--
Summary: Evaluate Azure Pipelines as a CI tool for Flink
Key: FLINK-13978
URL: https://issues.apache.org/jira/browse/FLINK-13978
Project: Flink
Issue
ts here;
> I would prefer if we only activate it once things are confirmed to be
> working.
>
> For observation purposes, we could also add it to flink-ci with
> notifications to people who are interested in this experiment.
> This wouldn't impact CiBot.
>
> On 03/09/2019 1
ensure that contributor builds are still running in a reasonable time?
>
> As an example of this happening on Travis, contributors currently cannot
> run all e2e tests since they timeout, but on apache we have a larger
> timeout.
>
> On 03/09/2019 18:57, Robert Metzger wrote:
>
.), nice docker support, plenty of free build resources for
open source projects, ...)
Best,
Robert
On Mon, Aug 19, 2019 at 5:12 PM Robert Metzger wrote:
> Hi all,
>
> I have summarized all arguments mentioned so far + some additional
> research into a Wiki page here:
> https://c
Thanks a lot for your summary Chesnay.
I agree with you that we have no consensus in the community for splitting
up the repository immediately, and I agree with you that we should have a
separate discussion about reducing the build time (which is already making
good progress).
Also, I will keep
t; Jiangjie (Becket) Qin
>
> On Thu, Aug 22, 2019 at 12:11 PM Robert Metzger
> wrote:
>
> > I have started a Wiki page (editable by all) for collecting ideas for
> > Bylaws changes, so that we can batch changes together and then vote on
> > them:
> >
> https:/
Jan, will you be able to test this issue on the now-released Flink 1.9 with
the new UI?
What parallelism is needed to reproduce the issue?
On Thu, Aug 15, 2019 at 1:59 PM Chesnay Schepler wrote:
> I remember an issue regarding the watermark fetch request from the WebUI
> exceeding some HTTP
) Qin
>
> On Tue, Aug 13, 2019 at 1:29 PM Robert Metzger
> wrote:
>
> > Hi Becket,
> > I've applied the proposed change to the document:
> >
> >
> https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=120731026=20=19
> >
> > I wou
he end-to-end tests use the shade plugin to package the jars for testing.
>
> Aljoscha
>
> > On 18. Aug 2019, at 19:52, Robert Metzger wrote:
> >
> > Hi all,
> >
> > I wanted to understand the impact of the hardware we are using for
> running
> >
provide support, if needed.
>
> Marta
>
> On Sun, Aug 18, 2019 at 4:46 PM Stephan Ewen wrote:
>
> > I could help with that.
> >
> > On Fri, Aug 16, 2019 at 2:36 PM Robert Metzger
> > wrote:
> >
> > > Flink 1.9 is feature freezed and almost releas
Hi all,
I wanted to understand the impact of the hardware we are using for running
our tests. Each travis worker has 2 virtual cores, and 7.5 gb memory [1].
They are using Google Cloud Compute Engine *n1-standard-2* instances.
Running a full "mvn clean verify" takes *03:32 h* on such a machine
Flink 1.9 is feature freezed and almost released.
I guess it makes sense to update the roadmap on the website again.
Who feels like having a good overview of what's coming up?
On Tue, May 7, 2019 at 4:33 PM Fabian Hueske wrote:
> Yes, that's a very good proposal Jark.
> +1
>
> Best, Fabian
>
>
Robert Metzger created FLINK-13739:
--
Summary: BinaryRowTest.testWriteString() fails in some environments
Key: FLINK-13739
URL: https://issues.apache.org/jira/browse/FLINK-13739
Project: Flink
Robert Metzger created FLINK-13738:
--
Summary: NegativeArraySizeException in LongHybridHashTable
Key: FLINK-13738
URL: https://issues.apache.org/jira/browse/FLINK-13738
Project: Flink
Issue
Has anybody verified the inclusion of all bundled dependencies into the
NOTICE files?
I'm asking because we had some issues with that in the last release(s).
On Wed, Aug 14, 2019 at 5:31 PM Aljoscha Krettek
wrote:
> +1
>
> I did some testing on a Google Cloud Dataproc cluster (it gives you a
>
Congratulations! Very happy to have you onboard :)
On Wed, Aug 14, 2019 at 4:06 PM Kostas Kloudas wrote:
> Congratulations Andrey!
> Well deserved!
>
> Kostas
>
> On Wed, Aug 14, 2019 at 4:04 PM Yun Tang wrote:
> >
> > Congratulations Andrey.
> >
> > Best
> > Yun Tang
> >
It seems that this FLIP doesn't have a Wiki page yet [1], even though it is
already partially implemented [2]
We should try to stick more to the FLIP process to manage the project more
efficiently.
[1]
https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals
[2]
Hi all,
I've opened a pull request for the release announcement. I'm looking
forward to your review & feedback:
https://github.com/apache/flink-web/pull/244
On Fri, Aug 9, 2019 at 6:27 PM Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> Update: voting on RC2 for Apache Flink 1.9.0 has started:
>
>
es
> >>>>>>> (like
> >>>>>>>>> the
> >>>>>>>>>>>>> DataSet API for instance or the legacy DataSet/DataStream
> >>>>>> Python
> >>>>>>>>>> APIs)?
> >>>>>>>>>&g
>
> > That's a good suggestion. Will you help to change the permission on that
> > page?
> >
> > Thanks,
> >
> > Jiangjie (Becket) Qin
> >
> > On Mon, Aug 12, 2019 at 2:41 PM Robert Metzger
> > wrote:
> >
> > > Thanks for starting the
Thanks a lot for starting the discussion Chesnay!
I would like to throw in another aspect into the discussion: What if we
consider this repo split as a first step towards making connectors, machine
learning, gelly, table/SQL? independent projects within the ASF, with their
own mailing lists,
Thanks for starting the vote.
How about putting a specific version in the wiki up for voting, or
restricting edit access to the page to the PMC?
There were already two changes (very minor) to the page since the vote has
started:
Congratulations!
On Wed, Aug 7, 2019 at 1:09 PM highfei2...@126.com
wrote:
> Congrats Hequn!
>
> Best,
> Jeff Yang
>
>
> Original Message
> Subject: Re: [ANNOUNCE] Hequn becomes a Flink committer
> From: Piotr Nowojski
> To: JingsongLee
> CC: Biao Liu ,Zhu Zhu ,Zili Chen ,Jeff
>
> > > > >> It is super easy to use for contributors as they don't need to
> keep
> > > any
> > > > >> particular coding style in mind and they can only focus on
> > > functionality
> > > > >> they want to fix, and it's also grea
The bot now warns if a pull request has been linked to an unassigned Jira
ticket. (It also puts a warning if no docs, no zh-docs have been touched,
or if a pom.xml file has been touched)
On Mon, Apr 15, 2019 at 3:11 PM Robert Metzger wrote:
> I will add such a feature to the bot!
>
&g
The mailing list has been created, you can now subscribe to it.
On Wed, Jul 24, 2019 at 1:43 PM Jark Wu wrote:
> Thanks Robert for helping out that.
>
> Best,
> Jark
>
> On Wed, 24 Jul 2019 at 19:16, Robert Metzger wrote:
>
> > I've requested the creation of the l
I've requested the creation of the list, and made Jark, Chesnay and me
moderators of it.
On Wed, Jul 24, 2019 at 1:12 PM Robert Metzger wrote:
> @Jark: Yes, I will request the creation of a mailing list!
>
> On Tue, Jul 23, 2019 at 4:48 PM Hugo Louro wrote:
>
>> +1
>&
> >> On Tue, Jul 23, 2019 at 1:59 PM Hequn Cheng
> wrote:
> >>
> >> Hi Jark,
> >>
> >> Good idea. +1!
> >>
> >>> On Tue, Jul 23, 2019 at 6:23 PM Jark Wu wrote:
> >>>
> >>> Thank you all for your posit
Hi all,
On behalf of the Flink PMC, I'm happy to announce that Kete Young is now
part of the Apache Flink Project Management Committee (PMC).
Kete has been a committer since February 2017, working a lot on Table API /
SQL. He's currently co-managing the 1.9 release! Thanks a lot for your work
l — this turned out amazing!
>>>
>>> Marta
>>>
>>> On Thu, Jul 18, 2019 at 10:57 AM Congxian Qiu
>>> wrote:
>>>
>>> > Robert and Daryl, thanks for the great work, I tried the website and
>>> filed
>>> > s
+1
On Mon, Jul 22, 2019 at 10:27 AM Biao Liu wrote:
> +1, make sense to me.
> Mailing list seems to be a more "community" way.
>
> Timo Walther 于2019年7月22日周一 下午4:06写道：
>
> > +1 sounds good to inform people about instabilities or other issues
> >
> > Regards,
> > Timo
> >
> >
> > Am 22.07.19 um
Hey all,
We've added another committer to the Flink project: Zhijiang Wang.
Congratulations Zhijiang!
Best,
Robert
(on behalf of the Flink PMC)
t;
> > >>>>>> -
> > >>>>>> Re: Chesnay
> > >>>>>>
> > >>>>>> The emeritus stuff seems like unnecessary noise.
> > >>>>>> As Till mentioned, this is
times in a row :)
>>> > >
>>> > > On 18/07/2019 12:32, Zili Chen wrote:
>>> > > > Robert,
>>> > > >
>>> > > > Thanks for your effort. Rejecting contributor permission request
>>> > > > with a nice message and pointing them to the anno
the email to the user@ list.
It is okay for me if you do that :)
On Thu, Jul 18, 2019 at 9:47 PM Bowen Li wrote:
> shall we announce in user ML too? Users who are used to assign tickets to
> themselves should also be aware of this change
>
> On Thu, Jul 18, 2019 at 3:06 AM Robert Metz
them
to my announcement.
What do you think?
[1]
https://lists.apache.org/thread.html/4ed570c7110b7b55b5c3bd52bb61ff35d5bda88f47939d8e7f1844c4@%3Cdev.flink.apache.org%3E
On Thu, Jul 4, 2019 at 1:21 PM Robert Metzger wrote:
> This is the Jira ticket I opened
> https://issues.apache.org/jira/br
601 - 700 of 1666 matches
Mail list logo
