Guowei Ma created FLINK-15032:
-
Summary: Remove the eagerly serialization from
`RemoteRpcInvocation`
Key: FLINK-15032
URL: https://issues.apache.org/jira/browse/FLINK-15032
Project: Flink
Guowei Ma created FLINK-14991:
-
Summary: Export `FLINK_HOME` environment variable to all the
entrypoint
Key: FLINK-14991
URL: https://issues.apache.org/jira/browse/FLINK-14991
Project: Flink
Congratulations, Becket!
Best,
Guowei
Steven Wu 于2019年11月1日周五 上午6:20写道:
> Congratulations, Becket!
>
> On Wed, Oct 30, 2019 at 9:51 PM Shaoxuan Wang wrote:
>
> > Congratulations, Becket!
> >
> > On Mon, Oct 28, 2019 at 6:08 PM Fabian Hueske wrote:
> >
> > > Hi everyone,
> > >
> > > I'm happy
Guowei Ma created FLINK-14467:
-
Summary: Let MesosJobClusterEntrypoint use user code class loader
Key: FLINK-14467
URL: https://issues.apache.org/jira/browse/FLINK-14467
Project: Flink
Issue
Guowei Ma created FLINK-14466:
-
Summary: Let YarnJobClusterEntrypoint use user code class loader
Key: FLINK-14466
URL: https://issues.apache.org/jira/browse/FLINK-14466
Project: Flink
Issue Type
Guowei Ma created FLINK-14465:
-
Summary: Let StandaloneJobClusterEntrypoint use user code class
loader
Key: FLINK-14465
URL: https://issues.apache.org/jira/browse/FLINK-14465
Project: Flink
Congratulations Zili !
Best,
Guowei
Fabian Hueske 于2019年9月11日周三 下午7:02写道:
> Congrats Zili Chen :-)
>
> Cheers, Fabian
>
> Am Mi., 11. Sept. 2019 um 12:48 Uhr schrieb Biao Liu :
>
>> Congrats Zili!
>>
>> Thanks,
>> Biao /'bɪ.aʊ/
>>
>>
>>
>> On Wed, 11 Sep 2019 at 18:43, Oytun Tez wrote:
>>
Guowei Ma created FLINK-13993:
-
Summary: Using FlinkUserCodeClassLoaders to load the user class in
the perjob mode
Key: FLINK-13993
URL: https://issues.apache.org/jira/browse/FLINK-13993
Project: Flink
Thanks Yun for bringing up this discussion and very thanks for all the deep
thoughts!
For now, I think this discussion contains two scenarios: one if for
iteration library support and the other is for SQL join support. I think
both of the two scenarios are useful but they seem to have different
t;
> Cheers,
> Till
>
> On Fri, Aug 16, 2019 at 10:27 AM Guowei Ma wrote:
>
> > Hi,
> > -1
> > We have a benchmark job, which includes a two-input operator.
> > This job has a big performance regression using 1.9 compared to 1.8.
> > It's still not very
Hi,
-1
We have a benchmark job, which includes a two-input operator.
This job has a big performance regression using 1.9 compared to 1.8.
It's still not very clear why this regression happens.
Best,
Guowei
Yu Li 于2019年8月16日周五 下午3:27写道:
> +1 (non-binding)
>
> - checked release notes: OK
> -
Guowei Ma created FLINK-13480:
-
Summary: Export SlotManager status at debug mode.
Key: FLINK-13480
URL: https://issues.apache.org/jira/browse/FLINK-13480
Project: Flink
Issue Type: Bug
Hi,
1. Currently, much work in FLINK-4256 is about failover improvements in the
bouded dataset scenario.
2. For the streaming scenario, a new shuffle plugin + proper failover
strategy could avoid the "stop-the-word" recovery.
3. We have already done many works about the new shuffle in the old
Guowei Ma created FLINK-13426:
-
Summary: TaskExecutor uses the wrong Registrationid in the
heartbeat with RM.
Key: FLINK-13426
URL: https://issues.apache.org/jira/browse/FLINK-13426
Project: Flink
Congratulations Kurt!
发自我的 iPhone
> 在 2019年7月23日,下午7:13,Bo WANG 写道:
>
> Congratulations Kurt!
>
>
> Best,
>
> Bo WANG
>
>
>> On Tue, Jul 23, 2019 at 5:24 PM Robert Metzger wrote:
>>
>> Hi all,
>>
>> On behalf of the Flink PMC, I'm happy to announce that Kete Young is now
>> part of the
Congratulations Zhijiang
发自我的 iPhone
> 在 2019年7月23日,上午12:55,Xuefu Z 写道:
>
> Congratulations, Zhijiang!
>
>> On Mon, Jul 22, 2019 at 7:42 AM Bo WANG wrote:
>>
>> Congratulations Zhijiang!
>>
>>
>> Best,
>>
>> Bo WANG
>>
>>
>> On Mon, Jul 22, 2019 at 10:12 PM Robert Metzger
>> wrote:
>>
Congrats Becket!
Best,
Guowei
Terry Wang 于2019年7月18日周四 下午5:17写道:
> Congratulations Becket!
>
> > 在 2019年7月18日,下午5:09,Dawid Wysakowicz 写道:
> >
> > Congratulations Becket! Good to have you onboard!
> >
> > On 18/07/2019 10:56, Till Rohrmann wrote:
> >> Congrats Becket!
> >>
> >> On Thu, Jul
Congratulations, Jincheng !
Best,
Guowei
zhisheng <173855...@qq.com> 于2019年6月25日周二 下午6:32写道:
> Congratulations, Jincheng
>
>
>
> ---Original---
> From: "Fan Liya"
> Date: Tue, Jun 25, 2019 18:23 PM
> To: "dev";
> Subject: Re: [ANNOUNCE] Jincheng Sun is now part of the Flink PMC
>
>
>
Thanks Gary for sharing the documents to the community.
The idea makes scheduler more flexible.
Best,
Guowei
Till Rohrmann 于2019年4月13日周六 上午12:21写道:
> Thanks for sharing the current state of the scheduler refactorings with the
> community Gary. The proposed changes look good to me and, hence,
Congratulations!
Thanks Aljoscha and all contributors!
Best,
Guowei
Jark Wu 于2019年4月10日周三 下午5:47写道:
> Cheers!
>
> Thanks Aljoscha and all others who make 1.8.0 possible.
>
> On Wed, 10 Apr 2019 at 17:33, vino yang wrote:
>
> > Great news!
> >
> > Thanks Aljoscha for being the release
Guowei Ma created FLINK-11985:
-
Summary: Remove ignored command line parameter from yarn_setup.md
Key: FLINK-11985
URL: https://issues.apache.org/jira/browse/FLINK-11985
Project: Flink
Issue
ome cleanup of the
> > Operator Config or the Operator Chain?
> >
> > Best,
> > Stephan
> >
> >
> > On Sun, Feb 10, 2019 at 7:25 AM Guowei Ma wrote:
> >
> >> 2019.2.10
> >>
> >>
> >> Hi,Stephan
> >>
> &g
thanks for starting this discussion. It is a very cool feature.
+1 for the FLIP
Best
Guowei
jincheng sun 于2019年2月13日周三 上午9:35写道:
> Thank you for starting the discussion about cancel-with-savepoint Kostas.
>
> +1 for the FLIP.
>
> Cheers,
> Jincheng
>
> Fabian Hueske 于2019年2月13日周三 上午4:31写道:
>
ould still work if an input ends.
> There are cases where some state in the operator that is only relevant as
> long as an input still has data (like in symmetric joins) and the timers
> are relevant to that state.
> When the state is dropped, the timers should also be dropped, but that i
2. Notify "StreamOperator" that an input has ended.
This proposal was discussed with Piotr Nowojski, Kostas Kloudas, Haibo Sun
offlline.
It will be great to hear the feed backs and suggestions from the community.
Please kindly share your comments and suggestions.
Best
GuoWei Ma.
Enhance Ope
Thanks to zhijiang for a detailed explanation. I would do some supplements
Blink has indeed solved this particular problem. This problem can be
identified in Blink and the upstream will be restarted by Blink
thanks
zhijiang 于2019年1月25日周五 下午12:04写道:
> Hi Bo,
>
> Your mentioned problems can be
+1
This not only helps Chinese users but also helps the community to collect more
feedback and scenarios.
> 在 2019年1月25日,上午2:29,Zhang, Xuefu 写道:
>
> +1 on the idea. This will certainly help promote Flink in China industries.
> On a side note, it would be great if anyone in the list can help
Hi, all
Thanks to Haibo for initiating this discussion in the community.
- Relationship of DataStream, DataSet, and Table API
Table/DataStream/Dataset does have different aspects. For example,
DataStream can access State and Table cannot. DataStream can be easily
extended by users because they
thanks yingjie to share this doc and I think this is very important feature
for production.
As you mentioned in your document, an unhealthy node can cause a TM
startup failure but cluster management may offer the same node for some
reason. (I have encountered such a scenario in our production
source API concern. In fact, that's what we are working on right
> now
> >>> as improvement to the existing consumer: Each shard consumer thread
> will
> >>> push to a queue, the consumer main thread will poll the queue(s). It is
> >>> essentially a mapping
Hi,
Thanks Aljoscha for this FLIP.
1. I agree with Piotr and Becket that the non-blocking source is very
important. But in addition to `Future/poll`, there may be another way to
achieve this. I think it may be not very memory friendly if every advance
call return a Future.
public interface
Guowei Ma created FLINK-6072:
Summary: TestCase CheckpointStateRestoreTest::testSetState should
be fail
Key: FLINK-6072
URL: https://issues.apache.org/jira/browse/FLINK-6072
Project: Flink
Hi,Albert
I think that the futures may be lost if the machine is down for some reasons.
So simply using the futures may not be acceptable in production.
I hope this is helpful.
Thanks
> 在 2016年9月16日,下午3:01,alghimo 写道:
>
> Hi Timo,
>
> Thank you for the fast
301 - 333 of 333 matches
Mail list logo