回复: flink KeyedBroadcastProcessFunction 不能触发onTimer
而且我发现查找了下 KeyedProcessFunction 的onTimer引用对应如下:
KeyedBroadcastProcessFunction 的onTimer引用对应如下:
KeyedProcessFunction 的onTimer方法签名是这样的:
public void onTimer(long timestamp, OnTimerContext ctx, Collector out)
throws Exception {}
KeyedBroadcastProcessFunction 的onTimer方法签名是这样的:
public void onTimer(final long timestamp, final OnTimerContext ctx, final
Collector out) throws Exception {
// the default implementation does nothing.
}
athlon...@gmail.com
发件人： athlon...@gmail.com
发送时间： 2019-08-14 10:14
收件人： user-zh
主题： flink KeyedBroadcastProcessFunction 不能触发onTimer
以下是我写了的一段代码,在 processElement 中每次进来一条日志就注册一次 onTimer事件
ctx.timerService().registerEventTimeTimer(value.getWindowEnd() + 1L);
如果onTimer触发则说明窗口内所有日志都被处理然后我要对窗口内的所有数据进行ctr计算但是onTimer不触发,我使用
KeyedProcessFunction 就可以触发,这是怎么回事呢?
public class TopCTRProcessFunction extends KeyedBroadcastProcessFunction, String> {
private ListState itemState;
private MapStateDescriptor ruleMapStateDescr =
new MapStateDescriptor<>("ruleMapState", String.class,
TopCTRInfo.class);
@Override
public void open(Configuration parameters) throws Exception {
ListStateDescriptor itemsStateDesc = new
ListStateDescriptor<>(
"itemState-state",
ItemViewCount.class);
itemState = getRuntimeContext().getListState(itemsStateDesc);
}
@Override
public void close() throws Exception {
super.close();
if (itemState != null) {
itemState.clear();
itemState = null;
}
}
@Override
public void processElement(ItemViewCount value, ReadOnlyContext ctx,
Collector out) throws Exception {
//计算ctr
value.setCtr(value.getClkCount() == 0 ? 0 : ((double)
value.getClkCount() / value.getImpCount() * 100));
itemState.add(value);
// 注册 windowEnd+1 的 EventTime Timer, 当触发时，说明收齐了属于windowEnd窗口的所有商品数据
ctx.timerService().registerEventTimeTimer(value.getWindowEnd() + 1L);
}
@Override
public void processBroadcastElement(Tuple2 value,
Context ctx, Collector out) throws Exception {
ctx.getBroadcastState(ruleMapStateDescr).put(value.f0, value.f1);
}
@Override
public void onTimer(long timestamp, OnTimerContext ctx, Collector
out) throws Exception {
ReadOnlyBroadcastState topCTRMap =
ctx.getBroadcastState(ruleMapStateDescr);
TopCTRInfo topCTRInfo =
topCTRMap.get(Constant.REDIS_BROADCAST_TOPCTR_KEY);
if (topCTRInfo == null) {
topCTRInfo = new TopCTRInfo();
}
List allItems = new ArrayList<>();
List jsonItems = new ArrayList<>();
for (ItemViewCount item : itemState.get()) {
if (item.getCtr() >= topCTRInfo.getCtrAlertThreshold()) {
allItems.add(item);
}
}
itemState.clear();
allItems.sort(new Comparator() {
@Override
public int compare(ItemViewCount o1, ItemViewCount o2) {
return (int) ((o2.getCtr() - o1.getCtr()) * 100);
}
});
int totalSize = topCTRInfo.getTopSize() > allItems.size() ?
allItems.size() : topCTRInfo.getTopSize();
for (int i = 0; i < totalSize; i++) {
jsonItems.add(allItems.get(i));
}
out.collect(JSON.toJSONString(jsonItems));
}
}
以下是可以触发onTimer的代码 使用 KeyedProcessFunction
.process(new KeyedProcessFunction() {
private final int topSize = 10;
private ListState itemState;
@Override
public void open(Configuration parameters) throws Exception {
super.open(parameters);
ListStateDescriptor itemsStateDesc = new
ListStateDescriptor<>(
"itemState-state",
ItemViewCount.class);
itemState = getRuntimeContext().getListState(itemsStateDesc);
}
@Override
public void processElement(ItemViewCount value, Context ctx,
Collector out) throws Exception {
//计算ctr
value.setCtr(value.getClkCount() == 0 ? 0 : ((double)
value.getClkCount() / value.getImpCount() * 100));
itemState.add(value);
// 注册 windowEnd+1 的 EventTime Timer, 当触发时，说明收齐了属于windowEnd窗口的所有商品数据
ctx.timerService().registerEventTimeTimer(value.getWindowEnd() + 1);
}
@Override
public void onTimer(long timestamp, OnTimerContext ctx, Collector
out) throws Exception {
super.onTimer(timestamp, ctx, out);
List allItems = new ArrayList<>();
List jsonItems = new ArrayList<>();
for (ItemViewCount item : itemState.get()) {
allItems.add(item);
}
itemState.clear();
allItems.sort(new Comparator() {
@Override
public int compare(ItemViewCount o1, ItemViewCount o2) {
return (int) ((o2.getCtr() - o1.getCtr()) * 100);
}
});
int totalSize = topSize > allItems.size() ? allItems.size() : topSize;
for (int i = 0; i < totalSize; i++) {
jsonItems.
flink KeyedBroadcastProcessFunction 不能触发onTimer
以下是我写了的一段代码,在 processElement 中每次进来一条日志就注册一次 onTimer事件
ctx.timerService().registerEventTimeTimer(value.getWindowEnd() + 1L);
如果onTimer触发则说明窗口内所有日志都被处理然后我要对窗口内的所有数据进行ctr计算但是onTimer不触发,我使用
KeyedProcessFunction 就可以触发,这是怎么回事呢?
public class TopCTRProcessFunction extends KeyedBroadcastProcessFunction, String> {
private ListState itemState;
private MapStateDescriptor ruleMapStateDescr =
new MapStateDescriptor<>("ruleMapState", String.class,
TopCTRInfo.class);
@Override
public void open(Configuration parameters) throws Exception {
ListStateDescriptor itemsStateDesc = new
ListStateDescriptor<>(
"itemState-state",
ItemViewCount.class);
itemState = getRuntimeContext().getListState(itemsStateDesc);
}
@Override
public void close() throws Exception {
super.close();
if (itemState != null) {
itemState.clear();
itemState = null;
}
}
@Override
public void processElement(ItemViewCount value, ReadOnlyContext ctx,
Collector out) throws Exception {
//计算ctr
value.setCtr(value.getClkCount() == 0 ? 0 : ((double)
value.getClkCount() / value.getImpCount() * 100));
itemState.add(value);
// 注册 windowEnd+1 的 EventTime Timer, 当触发时，说明收齐了属于windowEnd窗口的所有商品数据
ctx.timerService().registerEventTimeTimer(value.getWindowEnd() + 1L);
}
@Override
public void processBroadcastElement(Tuple2 value,
Context ctx, Collector out) throws Exception {
ctx.getBroadcastState(ruleMapStateDescr).put(value.f0, value.f1);
}
@Override
public void onTimer(long timestamp, OnTimerContext ctx, Collector
out) throws Exception {
ReadOnlyBroadcastState topCTRMap =
ctx.getBroadcastState(ruleMapStateDescr);
TopCTRInfo topCTRInfo =
topCTRMap.get(Constant.REDIS_BROADCAST_TOPCTR_KEY);
if (topCTRInfo == null) {
topCTRInfo = new TopCTRInfo();
}
List allItems = new ArrayList<>();
List jsonItems = new ArrayList<>();
for (ItemViewCount item : itemState.get()) {
if (item.getCtr() >= topCTRInfo.getCtrAlertThreshold()) {
allItems.add(item);
}
}
itemState.clear();
allItems.sort(new Comparator() {
@Override
public int compare(ItemViewCount o1, ItemViewCount o2) {
return (int) ((o2.getCtr() - o1.getCtr()) * 100);
}
});
int totalSize = topCTRInfo.getTopSize() > allItems.size() ?
allItems.size() : topCTRInfo.getTopSize();
for (int i = 0; i < totalSize; i++) {
jsonItems.add(allItems.get(i));
}
out.collect(JSON.toJSONString(jsonItems));
}
}
以下是可以触发onTimer的代码 使用 KeyedProcessFunction
.process(new KeyedProcessFunction() {
private final int topSize = 10;
private ListState itemState;
@Override
public void open(Configuration parameters) throws Exception {
super.open(parameters);
ListStateDescriptor itemsStateDesc = new
ListStateDescriptor<>(
"itemState-state",
ItemViewCount.class);
itemState = getRuntimeContext().getListState(itemsStateDesc);
}
@Override
public void processElement(ItemViewCount value, Context ctx,
Collector out) throws Exception {
//计算ctr
value.setCtr(value.getClkCount() == 0 ? 0 : ((double)
value.getClkCount() / value.getImpCount() * 100));
itemState.add(value);
// 注册 windowEnd+1 的 EventTime Timer, 当触发时，说明收齐了属于windowEnd窗口的所有商品数据
ctx.timerService().registerEventTimeTimer(value.getWindowEnd() + 1);
}
@Override
public void onTimer(long timestamp, OnTimerContext ctx, Collector
out) throws Exception {
super.onTimer(timestamp, ctx, out);
List allItems = new ArrayList<>();
List jsonItems = new ArrayList<>();
for (ItemViewCount item : itemState.get()) {
allItems.add(item);
}
itemState.clear();
allItems.sort(new Comparator() {
@Override
public int compare(ItemViewCount o1, ItemViewCount o2) {
return (int) ((o2.getCtr() - o1.getCtr()) * 100);
}
});
int totalSize = topSize > allItems.size() ? allItems.size() : topSize;
for (int i = 0; i < totalSize; i++) {
jsonItems.add(allItems.get(i));
}
out.collect(JSON.toJSONString(jsonItems));
}
})
athlon...@gmail.com
Re:Re: Re: [Discuss] What should the "Data Source" be translated into Chinese
好的，按照大家的意见统一对“Data Source”和“Data Sink”不翻译。
在 2019-08-14 05:19:13，"Yu Li" 写道：
>支持不翻译而在专有名词表中增加注释。
>
>从现有Flink翻译规范中的“术语表”来看，对于某些专有名词也是不翻译而只解释含义的，比如checkpoint。对于Data Source和Data
>Sink也建议采用同样的处理方式。
>
>PS. 这个是关于中文翻译的讨论，不太适合发到@dev邮件列表，希望大家能将讨论范围限定在中文邮件列表内，谢谢！
>
>Best Regards,
>Yu
>
>
>On Tue, 13 Aug 2019 at 15:02, WangHengwei wrote:
>
>> 我觉得《计算机科学技术名词》这个很有用，谢谢。
>>
>>
>>
>> Flink 翻译规范 [
>> https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications
>> ] 中有一些 Flink 专有名词的翻译规范，例如“State”翻译成“状态”，还有各种时间窗口，以及我们会把“Event”翻译成“事件”。
>>
>>
>> 晦涩或者非常专用的词汇不做翻译比较合适，例如”State
>> Backend“。但是如果可以找到比较优雅的中文词汇能够清晰代表含义的话，翻译过来有助于更好地理解，如果我们对于专有名词建立一个统一的译法就不会造成混乱，所以很想征求大家的意见。
>>
>>
>> “Data Source”翻译成数据源感觉比较通顺，而我在翻译时遇到很多与其相对的“Data
>> Sink“，从翻译者和阅读者的角度体会，如果翻译前者而不翻译后者感觉有些不一致。至少应该保持二者同时翻译或者不翻。
>>
>>
>> 想再听听大家的建议，非常感谢大家的回复。
>>
>> 在 2019-08-13 18:58:40，"Zili Chen" 写道：
>> >Source 和 Sink 的通译是 源 和 汇，data source 和 data sink 因此分别对应 数据源 和
>> >数据汇。出处可参见中国计算机协会的《计算机科学技术名词》，线上检索在这里[1]
>> >
>> >但是具体到 FLINK 的情况，实际上我建议所有 FLINK 专有名词都不要翻译，翻译反而增加理解难度。
>> >
>> >Best,
>> >tison.
>> >[1] http://www.termonline.cn/index.htm
>> >
>> >
>> >hsw 于2019年8月13日周二 下午6:46写道：
>> >
>> >> 赞同，想了半天没想到合适的中文翻译data sink
>> >>
>> >>
>> >>
>> >> --
>> >> 发件人：Jeff Zhang
>> >> 日 期：2019年08月13日 18:20:34
>> >> 收件人：
>> >> 抄 送：dafei1...@sina.com; dev
>> >> 主 题：Re: [Discuss] What should the "Data Source" be translated into
>> Chinese
>> >>
>> >> 不建议翻译
>> >>
>> >> Simon Su 于2019年8月13日周二 下午6:18写道：
>> >>
>> >> > 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
>> >> >
>> >> >
>> >> > Thanks,
>> >> > SImon
>> >> >
>> >> >
>> >> > On 08/13/2019 18:07， wrote：
>> >> > How about translate "data sink" into “数据漕”
>> >> > 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
>> >> > https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
>> >> >
>> >> >
>> >> >
>> >> > - 原始邮件 -
>> >> > 发件人：Kurt Young
>> >> > 收件人：dev , user-zh
>> >> > 主题：Re: [Discuss] What should the "Data Source" be translated into
>> Chinese
>> >> > 日期：2019年08月13日 16点44分
>> >> >
>> >> > cc user-zh mailing list, since there are lots of chinese speaking
>> people.
>> >> > Best,
>> >> > Kurt
>> >> > On Tue, Aug 13, 2019 at 4:02 PM WangHengwei
>> wrote:
>> >> > Hi all,
>> >> >
>> >> >
>> >> > I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
>> >> > Chinese. I have a problem.
>> >> >
>> >> > Usually we translate "Data Source" into "数据源" but there is no agreed
>> >> > translation for "Data Sink". Since it often appears in documents, I
>> think
>> >> > we'd better to have a unified translation. I have some alternatives,
>> e.g.
>> >> > "数据沉淀","数据归" or "数据终".
>> >> >
>> >> > Committer Xingcan Cui has a good suggestion for "数据汇" which
>> >> > corresponds to source ("数据源"). I asked Committer Jark Wu, he is also
>> fine
>> >> > with it. I think "数据汇" is a good representation of flow
>> charactiristics
>> >> so
>> >> > I would like to use it.
>> >> >
>> >> >
>> >> > I want to hear more thoughts from the community whether we should
>> >> > translate it and what it should be translated into.
>> >> >
>> >> >
>> >> > Thanks,
>> >> > WangHW
>> >> >
>> >>
>> >>
>> >> --
>> >> Best Regards
>> >>
>> >> Jeff Zhang
>> >>
>> >>
>>
Re: Re: [Discuss] What should the "Data Source" be translated into Chinese
支持不翻译而在专有名词表中增加注释。
从现有Flink翻译规范中的“术语表”来看，对于某些专有名词也是不翻译而只解释含义的，比如checkpoint。对于Data Source和Data
Sink也建议采用同样的处理方式。
PS. 这个是关于中文翻译的讨论，不太适合发到@dev邮件列表，希望大家能将讨论范围限定在中文邮件列表内，谢谢！
Best Regards,
Yu
On Tue, 13 Aug 2019 at 15:02, WangHengwei wrote:
> 我觉得《计算机科学技术名词》这个很有用，谢谢。
>
>
>
> Flink 翻译规范 [
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications
> ] 中有一些 Flink 专有名词的翻译规范，例如“State”翻译成“状态”，还有各种时间窗口，以及我们会把“Event”翻译成“事件”。
>
>
> 晦涩或者非常专用的词汇不做翻译比较合适，例如”State
> Backend“。但是如果可以找到比较优雅的中文词汇能够清晰代表含义的话，翻译过来有助于更好地理解，如果我们对于专有名词建立一个统一的译法就不会造成混乱，所以很想征求大家的意见。
>
>
> “Data Source”翻译成数据源感觉比较通顺，而我在翻译时遇到很多与其相对的“Data
> Sink“，从翻译者和阅读者的角度体会，如果翻译前者而不翻译后者感觉有些不一致。至少应该保持二者同时翻译或者不翻。
>
>
> 想再听听大家的建议，非常感谢大家的回复。
>
> 在 2019-08-13 18:58:40，"Zili Chen" 写道：
> >Source 和 Sink 的通译是 源 和 汇，data source 和 data sink 因此分别对应 数据源 和
> >数据汇。出处可参见中国计算机协会的《计算机科学技术名词》，线上检索在这里[1]
> >
> >但是具体到 FLINK 的情况，实际上我建议所有 FLINK 专有名词都不要翻译，翻译反而增加理解难度。
> >
> >Best,
> >tison.
> >[1] http://www.termonline.cn/index.htm
> >
> >
> >hsw 于2019年8月13日周二 下午6:46写道：
> >
> >> 赞同，想了半天没想到合适的中文翻译data sink
> >>
> >>
> >>
> >> --
> >> 发件人：Jeff Zhang
> >> 日 期：2019年08月13日 18:20:34
> >> 收件人：
> >> 抄 送：dafei1...@sina.com; dev
> >> 主 题：Re: [Discuss] What should the "Data Source" be translated into
> Chinese
> >>
> >> 不建议翻译
> >>
> >> Simon Su 于2019年8月13日周二 下午6:18写道：
> >>
> >> > 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
> >> >
> >> >
> >> > Thanks,
> >> > SImon
> >> >
> >> >
> >> > On 08/13/2019 18:07， wrote：
> >> > How about translate "data sink" into “数据漕”
> >> > 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> >> > https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
> >> >
> >> >
> >> >
> >> > - 原始邮件 -
> >> > 发件人：Kurt Young
> >> > 收件人：dev , user-zh
> >> > 主题：Re: [Discuss] What should the "Data Source" be translated into
> Chinese
> >> > 日期：2019年08月13日 16点44分
> >> >
> >> > cc user-zh mailing list, since there are lots of chinese speaking
> people.
> >> > Best,
> >> > Kurt
> >> > On Tue, Aug 13, 2019 at 4:02 PM WangHengwei
> wrote:
> >> > Hi all,
> >> >
> >> >
> >> > I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> >> > Chinese. I have a problem.
> >> >
> >> > Usually we translate "Data Source" into "数据源" but there is no agreed
> >> > translation for "Data Sink". Since it often appears in documents, I
> think
> >> > we'd better to have a unified translation. I have some alternatives,
> e.g.
> >> > "数据沉淀","数据归" or "数据终".
> >> >
> >> > Committer Xingcan Cui has a good suggestion for "数据汇" which
> >> > corresponds to source ("数据源"). I asked Committer Jark Wu, he is also
> fine
> >> > with it. I think "数据汇" is a good representation of flow
> charactiristics
> >> so
> >> > I would like to use it.
> >> >
> >> >
> >> > I want to hear more thoughts from the community whether we should
> >> > translate it and what it should be translated into.
> >> >
> >> >
> >> > Thanks,
> >> > WangHW
> >> >
> >>
> >>
> >> --
> >> Best Regards
> >>
> >> Jeff Zhang
> >>
> >>
>
Re: [Discuss] What should the "Data Source" be translated into Chinese
Hello ,
I think "数据末端" can also be a fine translation.
Fengyuchen
18813125717
> 在 2019年8月13日，下午5:27，WangHengwei 写道：
>
> Hi all,
>
>
>I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> Chinese. I have a problem.
>
>Usually we translate "Data Source" into "数据源" but there is no agreed
> translation for "Data Sink". Since it often appears in documents, I think
> we'd better to have a unified translation. I have some alternatives, e.g.
> "数据沉淀","数据归" or "数据终".
>
> Committer Xingcan Cui has a good suggestion for "数据汇" which corresponds
> to source ("数据源"). I asked Committer Jark Wu, he is also fine with it. I
> think "数据汇" is a good representation of flow charactiristics so I would like
> to use it.
>
>
>I want to hear more thoughts from the community whether we should
> translate it and what it should be translated into.
>
>
>Thanks,
>WangHW
回复: [Discuss] What should the "Data Source" be translated into Chinese
赞同，想了半天没想到合适的中文翻译data sink
--
发件人：Jeff Zhang
日 期：2019年08月13日 18:20:34
收件人：
抄 送：dafei1...@sina.com; dev
主 题：Re: [Discuss] What should the "Data Source" be translated into Chinese
不建议翻译
Simon Su 于2019年8月13日周二 下午6:18写道：
> 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
>
>
> Thanks,
> SImon
>
>
> On 08/13/2019 18:07， wrote：
> How about translate "data sink" into “数据漕”
> 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
>
>
>
> - 原始邮件 -
> 发件人：Kurt Young
> 收件人：dev , user-zh
> 主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
> 日期：2019年08月13日 16点44分
>
> cc user-zh mailing list, since there are lots of chinese speaking people.
> Best,
> Kurt
> On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> Hi all,
>
>
> I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> Chinese. I have a problem.
>
> Usually we translate "Data Source" into "数据源" but there is no agreed
> translation for "Data Sink". Since it often appears in documents, I think
> we'd better to have a unified translation. I have some alternatives, e.g.
> "数据沉淀","数据归" or "数据终".
>
> Committer Xingcan Cui has a good suggestion for "数据汇" which
> corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> with it. I think "数据汇" is a good representation of flow charactiristics so
> I would like to use it.
>
>
> I want to hear more thoughts from the community whether we should
> translate it and what it should be translated into.
>
>
> Thanks,
> WangHW
>
--
Best Regards
Jeff Zhang
Re: [Discuss] What should the "Data Source" be translated into Chinese
Hi, 这里有翻译的Convention, 可以作为参考, 个人建议这里不翻译
https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications
Zili Chen 于2019年8月13日周二 下午6:59写道：
> Source 和 Sink 的通译是 源 和 汇，data source 和 data sink 因此分别对应 数据源 和
> 数据汇。出处可参见中国计算机协会的《计算机科学技术名词》，线上检索在这里[1]
>
> 但是具体到 FLINK 的情况，实际上我建议所有 FLINK 专有名词都不要翻译，翻译反而增加理解难度。
>
> Best,
> tison.
> [1] http://www.termonline.cn/index.htm
>
>
> hsw 于2019年8月13日周二 下午6:46写道：
>
> > 赞同，想了半天没想到合适的中文翻译data sink
> >
> >
> >
> > --
> > 发件人：Jeff Zhang
> > 日 期：2019年08月13日 18:20:34
> > 收件人：
> > 抄 送：dafei1...@sina.com; dev
> > 主 题：Re: [Discuss] What should the "Data Source" be translated into
> Chinese
> >
> > 不建议翻译
> >
> > Simon Su 于2019年8月13日周二 下午6:18写道：
> >
> > > 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
> > >
> > >
> > > Thanks,
> > > SImon
> > >
> > >
> > > On 08/13/2019 18:07， wrote：
> > > How about translate "data sink" into “数据漕”
> > > 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> > > https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
> > >
> > >
> > >
> > > - 原始邮件 -
> > > 发件人：Kurt Young
> > > 收件人：dev , user-zh
> > > 主题：Re: [Discuss] What should the "Data Source" be translated into
> Chinese
> > > 日期：2019年08月13日 16点44分
> > >
> > > cc user-zh mailing list, since there are lots of chinese speaking
> people.
> > > Best,
> > > Kurt
> > > On Tue, Aug 13, 2019 at 4:02 PM WangHengwei
> wrote:
> > > Hi all,
> > >
> > >
> > > I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> > > Chinese. I have a problem.
> > >
> > > Usually we translate "Data Source" into "数据源" but there is no agreed
> > > translation for "Data Sink". Since it often appears in documents, I
> think
> > > we'd better to have a unified translation. I have some alternatives,
> e.g.
> > > "数据沉淀","数据归" or "数据终".
> > >
> > > Committer Xingcan Cui has a good suggestion for "数据汇" which
> > > corresponds to source ("数据源"). I asked Committer Jark Wu, he is also
> fine
> > > with it. I think "数据汇" is a good representation of flow charactiristics
> > so
> > > I would like to use it.
> > >
> > >
> > > I want to hear more thoughts from the community whether we should
> > > translate it and what it should be translated into.
> > >
> > >
> > > Thanks,
> > > WangHW
> > >
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
> >
>
Re: [Discuss] What should the "Data Source" be translated into Chinese
Source 和 Sink 的通译是 源 和 汇，data source 和 data sink 因此分别对应 数据源 和
数据汇。出处可参见中国计算机协会的《计算机科学技术名词》，线上检索在这里[1]
但是具体到 FLINK 的情况，实际上我建议所有 FLINK 专有名词都不要翻译，翻译反而增加理解难度。
Best,
tison.
[1] http://www.termonline.cn/index.htm
hsw 于2019年8月13日周二 下午6:46写道：
> 赞同，想了半天没想到合适的中文翻译data sink
>
>
>
> --
> 发件人：Jeff Zhang
> 日 期：2019年08月13日 18:20:34
> 收件人：
> 抄 送：dafei1...@sina.com; dev
> 主 题：Re: [Discuss] What should the "Data Source" be translated into Chinese
>
> 不建议翻译
>
> Simon Su 于2019年8月13日周二 下午6:18写道：
>
> > 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
> >
> >
> > Thanks,
> > SImon
> >
> >
> > On 08/13/2019 18:07， wrote：
> > How about translate "data sink" into “数据漕”
> > 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> > https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
> >
> >
> >
> > - 原始邮件 -
> > 发件人：Kurt Young
> > 收件人：dev , user-zh
> > 主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
> > 日期：2019年08月13日 16点44分
> >
> > cc user-zh mailing list, since there are lots of chinese speaking people.
> > Best,
> > Kurt
> > On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> > Hi all,
> >
> >
> > I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> > Chinese. I have a problem.
> >
> > Usually we translate "Data Source" into "数据源" but there is no agreed
> > translation for "Data Sink". Since it often appears in documents, I think
> > we'd better to have a unified translation. I have some alternatives, e.g.
> > "数据沉淀","数据归" or "数据终".
> >
> > Committer Xingcan Cui has a good suggestion for "数据汇" which
> > corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> > with it. I think "数据汇" is a good representation of flow charactiristics
> so
> > I would like to use it.
> >
> >
> > I want to hear more thoughts from the community whether we should
> > translate it and what it should be translated into.
> >
> >
> > Thanks,
> > WangHW
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>
>
Re: [Discuss] What should the "Data Source" be translated into Chinese
我也更倾向于不翻译 Data Source 和 Data Sink
Kurt Young 于2019年8月13日周二 下午6:21写道：
> "更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可" +1
>
> Best,
> Kurt
>
>
> On Tue, Aug 13, 2019 at 6:18 PM Simon Su wrote:
>
> > 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
> >
> >
> > Thanks,
> > SImon
> >
> >
> > On 08/13/2019 18:07， wrote：
> > How about translate "data sink" into “数据漕”
> > 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> > https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
> >
> >
> >
> > - 原始邮件 -
> > 发件人：Kurt Young
> > 收件人：dev , user-zh
> > 主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
> > 日期：2019年08月13日 16点44分
> >
> > cc user-zh mailing list, since there are lots of chinese speaking people.
> > Best,
> > Kurt
> > On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> > Hi all,
> >
> >
> > I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> > Chinese. I have a problem.
> >
> > Usually we translate "Data Source" into "数据源" but there is no agreed
> > translation for "Data Sink". Since it often appears in documents, I think
> > we'd better to have a unified translation. I have some alternatives, e.g.
> > "数据沉淀","数据归" or "数据终".
> >
> > Committer Xingcan Cui has a good suggestion for "数据汇" which
> > corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> > with it. I think "数据汇" is a good representation of flow charactiristics
> so
> > I would like to use it.
> >
> >
> > I want to hear more thoughts from the community whether we should
> > translate it and what it should be translated into.
> >
> >
> > Thanks,
> > WangHW
> >
>
Re: [Discuss] What should the "Data Source" be translated into Chinese
"更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可" +1
Best,
Kurt
On Tue, Aug 13, 2019 at 6:18 PM Simon Su wrote:
> 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
>
>
> Thanks,
> SImon
>
>
> On 08/13/2019 18:07， wrote：
> How about translate "data sink" into “数据漕”
> 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
>
>
>
> - 原始邮件 -
> 发件人：Kurt Young
> 收件人：dev , user-zh
> 主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
> 日期：2019年08月13日 16点44分
>
> cc user-zh mailing list, since there are lots of chinese speaking people.
> Best,
> Kurt
> On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> Hi all,
>
>
> I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> Chinese. I have a problem.
>
> Usually we translate "Data Source" into "数据源" but there is no agreed
> translation for "Data Sink". Since it often appears in documents, I think
> we'd better to have a unified translation. I have some alternatives, e.g.
> "数据沉淀","数据归" or "数据终".
>
> Committer Xingcan Cui has a good suggestion for "数据汇" which
> corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> with it. I think "数据汇" is a good representation of flow charactiristics so
> I would like to use it.
>
>
> I want to hear more thoughts from the community whether we should
> translate it and what it should be translated into.
>
>
> Thanks,
> WangHW
>
Re: [Discuss] What should the "Data Source" be translated into Chinese
不建议翻译
Simon Su 于2019年8月13日周二 下午6:18写道：
> 更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
>
>
> Thanks,
> SImon
>
>
> On 08/13/2019 18:07， wrote：
> How about translate "data sink" into “数据漕”
> 漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
> https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
>
>
>
> - 原始邮件 -
> 发件人：Kurt Young
> 收件人：dev , user-zh
> 主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
> 日期：2019年08月13日 16点44分
>
> cc user-zh mailing list, since there are lots of chinese speaking people.
> Best,
> Kurt
> On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> Hi all,
>
>
> I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> Chinese. I have a problem.
>
> Usually we translate "Data Source" into "数据源" but there is no agreed
> translation for "Data Sink". Since it often appears in documents, I think
> we'd better to have a unified translation. I have some alternatives, e.g.
> "数据沉淀","数据归" or "数据终".
>
> Committer Xingcan Cui has a good suggestion for "数据汇" which
> corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> with it. I think "数据汇" is a good representation of flow charactiristics so
> I would like to use it.
>
>
> I want to hear more thoughts from the community whether we should
> translate it and what it should be translated into.
>
>
> Thanks,
> WangHW
>
--
Best Regards
Jeff Zhang
Re: [Discuss] What should the "Data Source" be translated into Chinese
更倾向不去翻译Data Source和Data Sink, 通过用中文对其做解释即可
Thanks,
SImon
On 08/13/2019 18:07， wrote：
How about translate "data sink" into “数据漕”
漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
- 原始邮件 -
发件人：Kurt Young
收件人：dev , user-zh
主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
日期：2019年08月13日 16点44分
cc user-zh mailing list, since there are lots of chinese speaking people.
Best,
Kurt
On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
Hi all,
I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
Chinese. I have a problem.
Usually we translate "Data Source" into "数据源" but there is no agreed
translation for "Data Sink". Since it often appears in documents, I think
we'd better to have a unified translation. I have some alternatives, e.g.
"数据沉淀","数据归" or "数据终".
Committer Xingcan Cui has a good suggestion for "数据汇" which
corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
with it. I think "数据汇" is a good representation of flow charactiristics so
I would like to use it.
I want to hear more thoughts from the community whether we should
translate it and what it should be translated into.
Thanks,
WangHW
回复：Re: [Discuss] What should the "Data Source" be translated into Chinese
How about translate "data sink" into “数据漕”
漕，读作：cáo。汉字基本字义指通过水道运输粮食：漕运|漕粮。==>
https://baike.baidu.com/item/%E6%BC%95?forcehttps=1%3Ffr%3Dkg_hanyu
- 原始邮件 -
发件人：Kurt Young
收件人：dev , user-zh
主题：Re: [Discuss] What should the "Data Source" be translated into Chinese
日期：2019年08月13日 16点44分
cc user-zh mailing list, since there are lots of chinese speaking people.
Best,
Kurt
On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> Hi all,
>
>
> I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> Chinese. I have a problem.
>
> Usually we translate "Data Source" into "数据源" but there is no agreed
> translation for "Data Sink". Since it often appears in documents, I think
> we'd better to have a unified translation. I have some alternatives, e.g.
> "数据沉淀","数据归" or "数据终".
>
> Committer Xingcan Cui has a good suggestion for "数据汇" which
> corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> with it. I think "数据汇" is a good representation of flow charactiristics so
> I would like to use it.
>
>
> I want to hear more thoughts from the community whether we should
> translate it and what it should be translated into.
>
>
> Thanks,
> WangHW
Re: [Discuss] What should the "Data Source" be translated into Chinese
可以直接保留不用翻译吗？
Best,
Jingsong Lee
--
From:WangHengwei
Send Time:2019年8月13日(星期二) 11:50
To:user-zh
Subject:[Discuss] What should the "Data Source" be translated into Chinese
Hi all,
I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
Chinese. I have a problem.
Usually we translate "Data Source" into "数据源" but there is no agreed
translation for "Data Sink". Since it often appears in documents, I think we'd
better to have a unified translation. I have some alternatives, e.g.
"数据沉淀","数据归" or "数据终".
Committer Xingcan Cui has a good suggestion for "数据汇" which corresponds to
source ("数据源"). I asked Committer Jark Wu, he is also fine with it. I think
"数据汇" is a good representation of flow charactiristics so I would like to use
it.
I want to hear more thoughts from the community whether we should translate
it and what it should be translated into.
Thanks,
WangHW
Re:[Discuss] What should the "Data Source" be translated into Chinese
Hi all,
更倾向于不翻译 Data Source 和 Data Sink
Thanks,
SImon
On 08/13/2019 17:27，WangHengwei wrote：
Hi all,
I'm working on [FLINK-13405] Translate "Basic API Concepts" page into Chinese.
I have a problem.
Usually we translate "Data Source" into "数据源" but there is no agreed
translation for "Data Sink". Since it often appears in documents, I think we'd
better to have a unified translation. I have some alternatives, e.g.
"数据沉淀","数据归" or "数据终".
Committer Xingcan Cui has a good suggestion for "数据汇" which corresponds to
source ("数据源"). I asked Committer Jark Wu, he is also fine with it. I think
"数据汇" is a good representation of flow charactiristics so I would like to use
it.
I want to hear more thoughts from the community whether we should translate it
and what it should be translated into.
Thanks,
WangHW
[Discuss] What should the "Data Source" be translated into Chinese
Hi all,
I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
Chinese. I have a problem.
Usually we translate "Data Source" into "数据源" but there is no agreed
translation for "Data Sink". Since it often appears in documents, I think we'd
better to have a unified translation. I have some alternatives, e.g.
"数据沉淀","数据归" or "数据终".
Committer Xingcan Cui has a good suggestion for "数据汇" which corresponds to
source ("数据源"). I asked Committer Jark Wu, he is also fine with it. I think
"数据汇" is a good representation of flow charactiristics so I would like to use
it.
I want to hear more thoughts from the community whether we should translate
it and what it should be translated into.
Thanks,
WangHW
Re: flink on yarn，提交方式是per job的话，如何保证高可用？
YARN AM 包含了 Dispatcher/Resource Manager/JobManager，AM 挂掉的时候 YARN 会负责拉起来 一个相同配置的 AM。 Flink 自身的高可用，per job 模式下，CheckpointStore 基于 ZooKeeper 和 HDFS 来做，可以保证。 JobGraphStore 存在内存里，不是高可用的，但是每次新拉起来的 AM 都带有用户提交的 JobGraph 信息， 所以新拉起来的 Dispatcher 也能从中知道 JobGraph 的内容。 Best, tison. Zhenghua Gao 于2019年8月13日周二 下午5:02写道： > JM is restarted by YARN on failure [1]. > > [1] > > https://ci.apache.org/projects/flink/flink-docs-stable/ops/jobmanager_high_availability.html#yarn-cluster-high-availability > > *Best Regards,* > *Zhenghua Gao* > > > On Tue, Aug 13, 2019 at 4:51 PM 陈帅 wrote: > > > 请教一下：flink on yarn，提交方式是per job的话，如何保证高可用？ > > >
Re: flink on yarn，提交方式是per job的话，如何保证高可用？
JM is restarted by YARN on failure [1]. [1] https://ci.apache.org/projects/flink/flink-docs-stable/ops/jobmanager_high_availability.html#yarn-cluster-high-availability *Best Regards,* *Zhenghua Gao* On Tue, Aug 13, 2019 at 4:51 PM 陈帅 wrote: > 请教一下：flink on yarn，提交方式是per job的话，如何保证高可用？ >
flink on yarn，提交方式是per job的话，如何保证高可用？
请教一下：flink on yarn，提交方式是per job的话，如何保证高可用？
Re: [Discuss] What should the "Data Source" be translated into Chinese
cc user-zh mailing list, since there are lots of chinese speaking people.
Best,
Kurt
On Tue, Aug 13, 2019 at 4:02 PM WangHengwei wrote:
> Hi all,
>
>
> I'm working on [FLINK-13405] Translate "Basic API Concepts" page into
> Chinese. I have a problem.
>
> Usually we translate "Data Source" into "数据源" but there is no agreed
> translation for "Data Sink". Since it often appears in documents, I think
> we'd better to have a unified translation. I have some alternatives, e.g.
> "数据沉淀","数据归" or "数据终".
>
> Committer Xingcan Cui has a good suggestion for "数据汇" which
> corresponds to source ("数据源"). I asked Committer Jark Wu, he is also fine
> with it. I think "数据汇" is a good representation of flow charactiristics so
> I would like to use it.
>
>
> I want to hear more thoughts from the community whether we should
> translate it and what it should be translated into.
>
>
> Thanks,
> WangHW
