Re: [DISCUSS] Development of SQL OVER / Table API Row Windows for streaming tables

Hello Fabian, Your plan looks good, I totally agree with your points. While I am working on FLINK-4680, I had the similar concerns about the semantics of TumbleRows and SessionRows. It is much clear if we define these windows as SlideRows with PARTITION BY clause. Regarding to the implementation

Re: [DISCUSS] (Not) tagging reviewers

I totally agree with all of your ideas. Best wishes， SunJincheng. Stephan Ewen 于2017年1月16日 周一19:42写道： > Hi! > > > > I have seen that recently many pull requests designate reviews by writing > > "@personA review please" or so. > > > > I am personally quite strongly

Re: [DISCUSS] Table API / SQL indicators for event and processing time

Hi everyone, thanks for sharing your thoughts. I really like Timo’s proposal, and I have a few thoughts want to share. We want to keep the query same for batch and streaming. IMO. “process time” is something special to dataStream while it is not a well defined term for batch query. So it is kind

Re: [DISCUSS] Table API / SQL indicators for event and processing time

oved because any attribute can be marked as > event-time attribute (by calling 't.rowtime). > > Btw. A table source could still make the watermark configurable by offering > a respective interface. However, I'm not yet convinced that this needs to > be part of the Table A

Re: [DISCUSS] Table API / SQL indicators for event and processing time

> Xingcan > > On Wed, Mar 1, 2017 at 5:35 AM, Fabian Hueske <fhue...@gmail.com> wrote: > > > Hi Jincheng Sun, > > > > registering watermark functions for different attributes to allow each of > > them to be used in a window is an interesting idea.

Re: [ANNOUNCE] New Flink PMC member: Chesnay Schepler

Congrats Chesnay! 2017-07-30 1:43 GMT+08:00 Shaoxuan Wang : > Congratulations Chesnay! > > On Fri, Jul 28, 2017 at 10:05 PM, Greg Hogan wrote: > > > Developers, > > > > On behalf of the Flink PMC I am delighted to announce Chesnay Schepler as > > a

Re: Re: [ANNOUNCE] New Flink committer Jincheng Sun

.@gmail.com> > 发送时间：2017-07-11 14:27 > 主题：Re: [ANNOUNCE] New Flink committer Jincheng Sun > 收件人："Dev"<dev@flink.apache.org> > 抄送： > > Congratulations, Jincheng! > > > On Tue, Jul 11, 2017 at 2:01 PM, Zhuoluo Yang <zhuoluo@a

Re: [ANNOUNCE] New Flink PMC member: Tzu-Li (Gordon) Tai

Hi Gordon, Congratulations !!! Cheers, Jincheng 2017-07-10 22:44 GMT+08:00 Robert Metzger : > Hi Everybody, > > On behalf of the Flink PMC, I'm very excited to announce Gordon as the > latest addition to the Flink PMC. > > Gordon is a very active community member, helping

Feel confused for the illustration of tumbling window

Hi guys, Feel confused for the illustration of tumbling window, as follows: ​https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/windows.html#tumbling-windows https://ci.apache.org/projects/flink/flink-docs-release-1.3/fig/tumbling-windows.svg The Tumbling windows have a

Re: Feel confused for the illustration of tumbling window

cha Krettek <aljos...@apache.org>: > > > Hi, > > > > How do you mean? The windows in the illustration are not overlapping. > > > > I’m very happy about suggestions for improving this, though, if anyone > has > > one.  > > > > Best, > > Aljosch

Re: [CANCELLED] [VOTE] Release Apache Flink 1.3.1

Thanks @ Robert! @Fabian @Jack do you think the PRs are good to merged. I think we should try to merge these two PRs today. Best， SunJincheng 2017-06-19 20:56 GMT+08:00 Robert Metzger : > Thanks everybody for the testing of the RC1! > > I'm hereby cancelling the first RC

Re: [DISCUSS] Release Apache Flink 1.3.1

8:44:33 PM, Timo Walther (twal...@apache.org) wrote: > > FLINK-6881 and FLINK-6896 are merged. The Table API is ready for a new RC. > > Timo > > Am 19.06.17 um 17:00 schrieb jincheng sun: > > Thanks @Timo! > > > > 2017-06-19 22:02 GMT+08:00 Timo Walther <twal...@apach

Re: [ANNOUNCE] New Flink committer Shaoxuan Wang

Congratulations Shaoxuan. 2017-06-22 8:56 GMT+08:00 Zhangrucong : > Congrats Shaoxuan! > > -邮件原件- > 发件人: Fabian Hueske [mailto:fhue...@gmail.com] > 发送时间: 2017年6月22日 4:19 > 收件人: dev@flink.apache.org > 主题: [ANNOUNCE] New Flink committer Shaoxuan Wang > > Hi

Re: [DISCUSS] Reorganize Table API / SQL documentation

Hi, Fabian, Thanks for the sketch. The structure is pretty well to me, And glad to join in the discussion in google doc. Cheers, SunJincheng 2017-05-19 14:55 GMT+08:00 Shaoxuan Wang : > Hello Fabian, > Thanks for drafting the proposal. I like the entire organization in

Re: [DISCUSS] Release 1.3.0 RC1 (Non voting, testing release candidate)

Hi Robert, I have some checks to do and some test improve PRs ( https://issues.apache.org/jira/browse/FLINK-6619) need be done soon. Best, SunJincheng 2017-05-18 22:17 GMT+08:00 Greg Hogan : > The following tickets for 1.3.0 have a PR in need of review: > > [FLINK-6582]

Re: [VOTE] Release Apache Flink 1.3.0 (RC3)

Hi Robert, +1 to release: Check items have been checked, as follows: (flink-table) 1.Check that the JAVA and SCALA logical plans are consistent. 2.Check that the SQL and Table API logical plans are consistent. 3.Check that UDF, UDTF, and UDAF are working properly in group-windows and

Re: Stream sql example

hink you can open a JIRA. relation the error. I hope it can help you and best wish to you. welcome any feedback. :) Thanks, SunJincheng 2017-06-10 12:02 GMT+08:00 jincheng sun <sunjincheng...@gmail.com>: > Hi Dawid, > > For your case I think you can keep using: > > 【tEnv.t

Re: [DISCUSS] Table API / SQL features for Flink 1.4.0

Hi Fabian, Thanks for bring up this discuss. In order to enrich Flink's built-in scalar function, friendly user experience, I recommend adding as much scalar functions as possible in version 1.4 release. I have filed the JIRAs( https://issues.apache.org/jira/browse/FLINK-6810), and try my best to

Re: [ANNOUNCE] New committer: Dawid Wysakowicz

Congratulations Dawid! It's nice to see community teams getting stronger! Cheers, SunJincheng 2017-06-19 16:46 GMT+08:00 Fabian Hueske : > Congratulations Dawid! > It's great to have you on board. > > Cheers, Fabian > > 2017-06-19 10:40 GMT+02:00 Till Rohrmann

Re: [DISCUSS] Release Apache Flink 1.3.1

00 in 1.3.1. > > > > > > > > They are related to the metric system, and limit the size of > individual > > > metric name components > > > > as the default window operator names are so long they were causing > > > issues with file-system based > &

Re: [DISCUSS] Release Apache Flink 1.3.1

Hi Robert, From user mail-list I find 2 bugs as follows: https://issues.apache.org/jira/browse/FLINK-6886 https://issues.apache.org/jira/browse/FLINK-6896 I'm not sure if they are as the release blocker. But I think is better to merged those two PR. into 1.3.1 release. What do you think?

Re: [DISCUSS]: Integrating Flink Table API & SQL with CEP

Hi Jark, Dian, Thanks for bring up this discuss and share the prototype. +1 to push this great feature forward! Cheers, SunJincheng 2017-06-13 15:34 GMT+08:00 Jark Wu : > Thank you Yueting for pointing out the mistake in the prototype. I > accidentally introduced it when

Re: [DISCUSS] Releasing Flink 1.4.1

Thanks for starting the discussion Gordon. I think it is better to add the commits of `https://issues.apache.org/jira/browse/FLINK-8355` and `https://issues.apache.org/jira/browse/FLINK-8325` for table API & SQL. Because these two issues fixed commonly used `count (*)` bug and improve of

Re: Dynamic SessionWindow gaps

Hi, Dyana dynamic gap is very useful feature, Agree with the suggestion of Aljoscha, looking forward the PR. Best, Jincheng 2018-01-02 21:45 GMT+08:00 Aljoscha Krettek : > Hi, > > This sounds good! Could you please open a Jira Issue for this and then > open a PR against

Re: Creating a slide set for a Flink intro talk

@Fabian Hueske Thanks for create the slide. I think it is very important for the construction of the flink ecosystem. The content of the slide outline is very comprehensive. I think these are the things that the user wants to know. I will leave suggestions about detail. We continue to discuss it

Re: [DISCUSS] [Contributing] (3) - Review Tooling

Sounds good! @Fabian Hueske Fabian Hueske 于2018年10月18日周四 下午4:24写道： > Hi, > > I opened a PR to extend the PR description template [1]. > > @jincheng sun , I'd suggest to start a separate > discussion about a template for Jira ticket. Let's try to keep this thread > f

Re: [DISCUSS] [Contributing] (3) - Review Tooling

I like @Fabian Hueske 's proposal, currently design the template is pretty good idea. Because the template is convenient for contributors to follow the norms to community contributions. About templates, I think we also need an JIRA description template, In particular, in the case of current JIRA

[DISCUSS] Enhancing the functionality and productivity of Table API

Hi all, With the continuous efforts from the community, the Flink system has been continuously improved, which has attracted more and more users. Flink SQL is a canonical, widely used relational query language. However, there are still some scenarios where Flink SQL failed to meet user needs in

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

adoption of Table API. To this end, Table API still requires more efforts from every contributor in the community. We see great opportunity in improving our user’s experience from this work. Any feedback is welcome. Regards, Jincheng jincheng sun 于2018年11月1日周四 下午5:07写道： > Hi

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

01.11.18 um 13:12 schrieb Aljoscha Krettek: > > Hi Jincheng, > > > > these points sound very good! Are there any concrete proposals for > changes? For example a FLIP/design document? > > > > See here for FLIPs: > https://cwiki.apache.org/confluence/display/FLINK/Flink+

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

proposals for > changes? For example a FLIP/design document? > > See here for FLIPs: > https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals > > Best, > Aljoscha > > > On 1. Nov 2018, at 12:51, jincheng sun wrote: > > > > *I

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

could be done here. I am looking > forward to the upcoming FLIPs. > > Thanks, > > Jiangjie (Becket) Qin > > On Fri, Nov 2, 2018 at 12:10 AM jincheng sun > wrote: > > > Hi, Timo, > > I am very grateful for your feedback, and I am very excited when I hear >

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

: > > > > > Hi Jincheng, > > > > > > these points sound very good! Are there any concrete proposals for > > > changes? For example a FLIP/design document? > > > > > > See here for FLIPs: > > > > > > https://cwiki.apache.or

Re: [VOTE] Release 1.7.0, release candidate #1

Hi Till, Today when I do the CI before merge code, I find a instability test case: JobManagerHAProcessFailureRecoveryITCase.testDispatcherProcessFailure test fail. I'm not sure if this is issue should blocking the release 1.7, but I think it's best to find the cause and fix it before releasing

Re: [DISCUSS] Table API Enhancement Outline

w points that we need to have more discussions. > > > > > > > >- TableAggregateFunction - this is a very complex beast, > definitely > > > the > > > > most complex user defined objects we introduced so far. I think > > there > &

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

Hi Piotrek, Fabian: I am very glad to see your reply. Thank you very much Piotrek for asking very good questions. I will share my opinion: - The Enhancing TableAPI that I proposed is proposed for user friendliness. After enhancement, it will maintain the characteristics of TableAPI,

Re: [DISCUSS] Table API Enhancement Outline

>- GroupedTable.agg - does the group keys automatically appear in the >output? how about the case of windowing aggregation? > > Regards, > Xiaowei > > On Tue, Nov 6, 2018 at 6:25 PM jincheng sun > wrote: > > > Hi, Xiaowei, > > > > T

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

incheng, > > > > > > > > Thank you for the proposal! I think being able to define a process / > > > > co-process function in table API definitely opens up a whole new > level > > of > > > > applications using a unified API. > > >

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

ience Table API was always giving me the impression to > be a > > more sophisticated, syntactic-aware way to express relational operations. > > Looking forward to further discussion and collaborations on the FLIP doc. > > > > -- > > Rong > > > > On Sun, Nov

Re: [DISCUSS] Table API Enhancement Outline

Hi, Xiaowei, Thanks for bring up the discuss of Table API Enhancement Outline ! I quickly looked at the overall content, these are good expressions of our offline discussions. But from the points of my view, we should add the usage of public interfaces that we will introduce in this propose.

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

But if we support Table.drop() method for TableAPI, it will be a very > convenient method and let users stay in Table. > > Looking forward to the more detailed design and further discussion. > > Regards, > Jark > > jincheng sun 于2018年11月6日周二 下午1:05写道： > > > Hi Rong

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

end and improve Flink's > SQL support (within the bounds of the standard). > > Best, Fabian > > Am Di., 6. Nov. 2018 um 10:09 Uhr schrieb jincheng sun < > sunjincheng...@gmail.com>: > > > Hi Jark, > > Glad to see your feedback! > > That's Correct, The propo

Re: [DISCUSS] Table API Enhancement Outline

(or exactly?) one Scalar / TableFunction is used. > > Best, > Fabian > > Am Do., 8. Nov. 2018 um 19:25 Uhr schrieb jincheng sun < > sunjincheng...@gmail.com>: > > > Hi all, > > > > We are discussing very detailed content about this proposal. We are > trying &

Re: [VOTE] Release 1.7.0, release candidate #1

, Nov 8, 2018 at 7:19 PM jincheng sun > wrote: > > > Hi Till, > > > > Today when I do the CI before merge code, I find a instability test case: > > JobManagerHAProcessFailureRecoveryITCase.testDispatcherProcessFailure > test > > fail. > > I'm not sure if

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

ther, as mentioned by @hequn, > > SQL is a widely used language. It follows standards, is a > > descriptive language, and is easy to use > > > thus we could expect with the enhancement of SQL/Table API, Flink > becomes more friendly to users. > > Looking forward to the de

Re: [ANNOUNCE] Contributing Alibaba's Blink

Thanks Stephan! This is a very exciting news for the flink community. I recommend creating a branch for blink in the Flink repository. Just like feature development, the blink branch is a branch with many enhancements, and the enhanced functionality is continuously merged to the flink master.

Re: [VOTE] Release 1.7.1, release candidate #2

Hi Chesnay, +1(non-binding) - run `mvn clean install` locally with success - run all TestCases(both java and scala), except NettyEpollITCase in the flink-test module in IDEA locally with success (errors has checked in FLINK-11178) hequn Chen, tison and myself had check the test case error in

Re: [ANNOUNCE] Apache Flink 1.5.6 released

Thanks a lot for being our release manager Thomas. Thanks a lot for made this release possible! Cheers, Jincheng Thomas Weise 于2018年12月27日周四 上午4:03写道： > The Apache Flink community is very happy to announce the release of Apache > Flink 1.5.6, which is the final bugfix release for the Apache

Re: [DISCUSS] Enhance convenience of TableEnvironment in TableAPI/SQL

. At the SQL/TableAPI level, users don't need to know the existence of `BatchTableEnvironment` and `StreamTableEnvironment`. What do you think？ Thanks, Jincheng jincheng sun 于2018年12月12日周三 下午3:44写道： > HI Timo, > > Thanks for your feedback! And I'm glad to hear that you are already > th

Re: [DISCUSS] Enhance convenience of TableEnvironment in TableAPI/SQL

HI Timo, Thanks for your feedback! And I'm glad to hear that you are already thinking about import issues! 1. I commented on the solution you mentioned in FLINK-11067. I have the same questions with Dian Fu, about the design of compatibility in the google doc, I look forward to your reply. 2.

Re: [DISCUSS] Enhance convenience of TableEnvironment in TableAPI/SQL

Hi Xuefu, Thanks for your feedback, and mention the compatibility issues. You are right the change will result version incompatibility. And we my plan it's will be released in the version of 1.8.x. To be frank, we have considered the compatibility approach, which is to retain the current

Re: [VOTE] Release 1.7.1, release candidate #2

Hi Chesnay, Thanks for bring up the 1.7.1-rc2 release vote! I had do some test check as follows: 1. Local source code compilation [mvn clean install] [success] 2. Run all TestCases(both java and scala),except NettyEpollITCase in the flink-test module in IDEA [find some errors] 3. Remove the

Re: [ANNOUNCE] Apache Flink 1.6.3 released

Thanks a lot for being our release manager Gordon. Thanks a lot for made this release possible! Cheers, Jincheng Tzu-Li (Gordon) Tai 于2018年12月23日周日 下午9:35写道： > Hi, > > The Apache Flink community is very happy to announce the release of > Apache Flink 1.6.3, which is the third bugfix release

Re: [ANNOUNCE] Apache Flink 1.7.1 released

Thanks for being the release manager Chesnay! Thanks a lot for made this release possible! Thanks, Jincheng Chesnay Schepler 于2018年12月23日周日 上午3:34写道： > The Apache Flink community is very happy to announce the release of > Apache Flink 1.7.1, which is the first bugfix release for the Apache >

Re: [DISCUSS] Table API Enhancement Outline

ction if we want to select keys. We could to that with a short cut: > > val tabX3 = tab.window(Tumble ... as 'w) > .groupBy('w, 'k1, 'k2) > .flatAgg(tableAgg('a)) > .select('w.rowtime, 'k1, 'k2, '*) > > > Am Di., 27. Nov. 2018 um 10:46 Uhr schrieb jincheng sun < >

Re: [DISCUSS] Unified Core API for Streaming and Batch

Hi Haibo, Thank you for this great proposal！ Flink is a unified computing engine. It has been unified at the TableAPI and SQLAPI levels (not yet complete). It's greate If we can unify the DataSet API and DataStream API. I also want to convert to StreamTransformation in the SQL and Table API,

Re: delay one of the datastream when performing join operation on event-time and watermark

Hi Pakesh Kuma, I think you can using the interval-join, e.g.: orderStream .keyBy() .intervalJoin(invoiceStream.keyBy()) .between(Time.minutes(-5), Time.minutes(5)) The semantics of interval-join and detailed usage description can refer to

[DISCUSS] Enhance convenience of TableEnvironment in TableAPI/SQL

Hi All, According to the feedback from users, the design of TableEnvironment is very inconvenient for users, and often mistakenly imported by IDE, especially for Java users, such as: ExecutionEnvironment env = ... BatchTableEnvironment tEnv = TableEnvironment.getTableEnvironment(env); The

Re: [DISCUSS] Creating last bug fix release for 1.5 branch

+1. There are incompatible improvements between 1.5.x and 1.6/1.7, so many 1.5.x users may not be willing to upgrade to 1.6 or 1.7 due to migration costs, so it makes sense to creating last bug fix release for 1.5 branch. Bests, Jincheng Jeff Zhang 于2018年12月10日周一 上午9:24写道： > +1, I think very

Re: [DISCUSS] Table API Enhancement Outline

s fine with me. > > The grouping columns (+window properties) are "side-passed" from the > > groupBy. > > > > So, IMO, both select('*) and select('k1, 'k2, 'w.rowtime, '*) have well > > defined semantics. But we can add these shortcuts later. > &

Re: [DISCUSS] Table API Enhancement Outline

fields (end, > start, rowtime). > Once we add a new property, it would need to be added to the composite > type. > Any query that relies on the composite type with three fields will fail > after adding a forth field. > > Best, Fabian > > Am Fr., 23. Nov. 2018 um 02

Re: [DISCUSS] Table API Enhancement Outline

'w in the resulting Table? Is it a regular field at all or just a > > > system field that disappears if it is not selected? > > > > > > IMO, the following syntax is shorter, more explicit, and better aligned > > > with the regular window.groupBy.select aggregati

Re: [DISCUSS] Table API Enhancement Outline

Hi shaoxuan & Hequn, Thanks for your suggestion，I'll file the JIRAs later. We can prepare PRs while continuing to move forward the ongoing discussion. Regards， Jincheng jincheng sun 于2018年11月21日周三 下午7:07写道： > Hi Piotrek, > Thanks for your feedback, and thanks for share your though

Re: [DISCUSS] Table API Enhancement Outline

Btw, we can start with JIRAs > > which we have agreed on. > > > > Best, > > Hequn > > > > On Tue, Nov 20, 2018 at 11:38 PM Shaoxuan Wang > wrote: > > > >> +1. I agree that we should open the JIRAs to start the work. We may > >> have bett

Re: [DISCUSS] Table API Enhancement Outline

k1, k2, col1, col2) > x.select(myUdf('w)) // fails because UDF expects (start, end, rowtime) and > not (start, end, rowtime, newProperty) > > Basically, every time when the composite type 'w is used as a whole. > > > Am Fr., 23. Nov. 2018 um 10:45 Uhr schrieb jincheng sun <

Re: Apply for Contributor Permission

Hi Fabian, I have a question that only PMC can manage Contributor permissions? Thanks, Jincheng Fabian Hueske 于2018年11月22日周四 下午5:52写道： > Hi, > > I gave you contributor permissions. > Looking forward to your contributions. > > Best, Fabian > > Am Do., 22. Nov. 2018 um 04:26 Uhr schrieb Wei

Re: [VOTE] Release 1.7.0, release candidate #2

Hi Hequn, Thanks for check the test, +1 this not a blocker of the release. and I'll merge your PR. Best, Jincheng Hequn Cheng 于2018年11月22日周四 下午4:35写道： > Hi, > > I'm trying to check if the source release is building properly. And found > that NonHAQueryableStateFsBackendITCase failed when run

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

Best, Fabian > > Am Mi., 14. Nov. 2018 um 02:02 Uhr schrieb jincheng sun < > sunjincheng...@gmail.com>: > > > Hi Piotrek, Fabian: > > > > I am very glad to see your reply. Thank you very much Piotrek for asking > > very good questions. I will share my opinion

Re: Apply for Contributor Permission

I see, thanks Fabian ! Fabian Hueske 于2018年11月22日周四 下午6:10写道： > Yes, I think so. > Currently, only PMC members are in the Jira Admin group. > > Best, Fabian > > > Am Do., 22. Nov. 2018 um 10:56 Uhr schrieb jincheng sun < > sunjincheng...@gmail.com>: > > &g

Re: [DISCUSS] Table API Enhancement Outline

unnest(), ‘b, scalarG(‘c)) > or > table.flatMap(F(‘a), ‘b, scalarG(‘c)) > > Could work and be more or less a syntax sugar for cross apply. > > Piotrek > > > On 21 Nov 2018, at 12:16, jincheng sun wrote: > > > > Hi shaoxuan & Hequn, > > > >

Re: [DISCUSS] Support Interactive Programming in Flink Table API

Hi Jiangjie, Thanks for initiating this great proposal！ Interactive Programming is very useful and user friendly in case of your examples. Moreover， especially when a business has to be executed in several stages with dependencies，such as the pipeline of Flink ML, in order to utilize the

Re: [DISCUSS] Table API Enhancement Outline

ggregateFunction` > > vs > > table.groupBy(‘k).flatAggregate(tableAggregateFunction(‘v)) => both > result > > of `tableAggregateFunction` plus key (and an optional window context ?) > > > > Thus I think we have to now decide which way we want to jump, sin

Re: [DISCUSS] Long-term goal of making flink-table Scala-free

Hi Timo, Thanks for initiating this great discussion. Currently when using SQL/TableAPI should include many dependence. In particular, it is not necessary to introduce the specific implementation dependencies which users do not care about. So I am glad to see your proposal, and hope when we

Re: [DISCUSS] Support Interactive Programming in Flink Table API

> Relying on a callback for the temp table for clean up is not very > > reliable. > > > There is no guarantee that it will be executed successfully. We may > risk > > > leaks when that happens. I think that it's safer to have an association > > > between temp

Re: [DISCUSS] Embracing Table API in Flink ML

Hi Weihua， Thanks for bring up this discuss! I quickly read the google doc，and I fully agree that ML can be well supported on TableAPI (at some stage in the future). In fact, Xiaowei and I have already brought up a discussion on enhancing the Table API. In the first phase, we will add support

Re: [DISCUSS] Table API Enhancement Outline

regate do > not return a Table but some kind of AggregatedTable that does not provide > any other function than select(). > > Am Mo., 26. Nov. 2018 um 01:12 Uhr schrieb jincheng sun < > sunjincheng...@gmail.com>: > > > Yes，I agree the problem is needs attention. IMO. It depends on how w

Re: [DISCUSS] Table API Enhancement Outline

e, Tuple, Row, and Map have disadvantages because the syntax > 'w.rowtime or 'w.end would not be supported. > > Am Di., 27. Nov. 2018 um 01:05 Uhr schrieb jincheng sun < > sunjincheng...@gmail.com>: > > > Before we have a good support for nest-table, may be forcing t

Re: [DISCUSS] Bot for stale PRs on GitHub

+1 for the bot solution！ and I think Timo‘s suggestion is very useful！ Thanks， Jincheng Timo Walther 于2019年1月11日 周五22:44写道： > Thanks for bringing up this discussion again. +1 for a bot solution. > However, we should discuss a good process for closing PRs. > > In many cases, PRs are closed not

Re: [ANNOUNCE] Contributing Alibaba's Blink

Thanks Stephan, The entire plan makes sense to me. Regarding the branch name, how about using "blink-flink-1.5" wich meant that the branche is based on flink-1.5. If the name is "blink-1.5", some users will think that this is the version number of the internal Blink of alibaba, and will not

Re: [DISCUSS] Towards a leaner flink-dist

Hi Chesnay, Thank you for the proposal. And i like it very much. +1 for the leaner distribution. About improve the "Download" page, I think we can add the connectors download link in the "Optional components" section which @Timo Walther mentioned above. Regards, Jincheng Chesnay Schepler

Re: [DISCUSS] FLIP-32: Restructure flink-table for future contributions

Hi Timo, Thanks a lot for bring up the FLIP-32 discussion and the very detailed implementation plan document ! Restructure `flink-table` is an important part of flink merge blink, looking forward to the JIRAs which will be opened ! Cheers， Jincheng Timo Walther 于2019年1月24日周四 下午9:06写道： > Hi

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

+1，I like the idea very much！ Robert Metzger 于2019年1月24日 周四19:15写道： > Hey all, > > I would like to create a new user support mailing list called " > user...@flink.apache.org" to cater the Chinese-speaking Flink community. > > Why? > In the last year 24% of the traffic on flink.apache.org came

Re: [DISCUSS] Python (and Non-JVM) Language Support in Flink

no yang 于2019年3月28日周四 下午2:44写道： > >> Hi jincheng, >> >> Thanks for activating this discussion again. >> I personally look forward to your design draft. >> >> Best, >> Vino >> >> jincheng sun 于2019年3月28日周四 下午12:16写道： >> >> >

[DISCUSS] FLIP-38 Support python language in flink TableAPI

Hi All, As Xianda brought up in the previous email, There are a large number of data analysis users who want flink to support Python. At the Flink API level, we have DataStreamAPI/DataSetAPI/TableAPI, the Table API will become the first-class citizen. Table API is declarative and can be

Re: [VOTE] Release 1.8.0, release candidate #4

because waiting for the dispatcher to come up times > out. I also noticed that this usually takes about 5-8 seconds on Travis, so > a 10 second timeout might be a bit low. I pushed commits to increase that > to 20 secs. Let’s see what will happen. > > I’ll keep you posted! > Aljoscha

Re: [DISCUSS] Introduction of a Table API Java Expression DSL

Thanks for bringing up this DISCUSS Timo! Java Expression DSL is pretty useful for java user. When we have the Java Expression DSL, Java API will become very rich and easy to use! +1 from my side. Best, Jincheng Dawid Wysakowicz 于2019年3月26日周二 下午5:08写道： > Hi, > > I really like the idea of

Re: [REMINDER] Please add entries for newly added dependencies to NOTICE file

Hi Aljoscha, Thanks for bringing this up. The release-1.8 we have been prepared 4 times RC, and in addition to one performance issue, all of the rest are NOTICE issues. We really need to pay attention on this. I agree with Ufuk, improve the `flink-bot` is a good idea. And the committer who merge

Re: [REMINDER] Please add entries for newly added dependencies to NOTICE file

Hi Aljoscha, Thanks for bringing this up. The release-1.8 we have been prepared 4 times RC, and in addition to one performance issue, all of the rest are NOTICE issues. We really need to pay attention on this. I think improve the `flink-bot Bowen Li 于2019年3月24日周日 下午2:04写道： > Hi, > > I agree

Re: [VOTE] Release 1.8.0, release candidate #4

Great thanks for preparing the RC4 of Flink 1.8.0, Aljoscha! +1 (non-binding) I checked the functional things as follows(Without performance verification): 1. Checking Artifacts： 1). Download the release source code - SUCCESS 2). Check Source release flink-1.8.0-src.tgz.sha512 -

Re: [DISCUSS] FLIP-38 Support python language in flink TableAPI

UDF support, and > what's > > timeline for adding DataStream API support? We would like to help and > > contribute as well as we do have similar need internally at our company. > > Thanks a lot. > > > > Shuyi > > > > On Tue, Apr 2, 2019 at 1:03 AM jinc

Re: [DISCUSS] FLIP-38 Support python language in flink TableAPI

i-lang UDF support, and what's > timeline for adding DataStream API support? We would like to help and > contribute as well as we do have similar need internally at our company. > Thanks a lot. > > Shuyi > > On Tue, Apr 2, 2019 at 1:03 AM jincheng sun > wrote: > > > Hi

Re: [DISCUSS] FLIP-38 Support python language in flink TableAPI

nks jincheng for driving this. Overall I agree with the approach, just > left a few comments for details. > > > > jincheng sun 于2019年4月2日周二 下午4:03写道： > > > Hi All, > > As Xianda brought up in the previous email, There are a large number of > > data analysis

Re: [DISCUSS] FLIP-38 Support python language in flink TableAPI

support but we want to > >> collaborate on that manner with the Beam community. I think this is also > >> the concern Thomas raised[2]. > >> > >> Let's make sure we do not contradict with what was said in[1]. Could you > >> elaborate more how does it

Re: [DISCUSS] FLIP-38 Support python language in flink TableAPI

Adding multi-lang support sounds a promising direction to > expand > > > the > > > > footprint of Flink. Do we have plan for adding Golang support? As > many > > > > backend engineers nowadays are familiar with Go, but probably not > Java > > as > &

Re: [DISCUSS] FLIP-38 Support python language in flink TableAPI

t; Thanks a lot for driving the FLIP, jincheng. The approach looks > > > > good. Adding multi-lang support sounds a promising direction to > expand > > > the > > > > footprint of Flink. Do we have plan for adding Golang support? As > many > >

Re: [DISCUSS] Python (and Non-JVM) Language Support in Flink

Hi everyone, Sorry to join in this discussion late. Thanks to Xianda Ke for initiating this discussion. I also enjoy the discussions by Max, Austin, Thomas, Shaoxuan and others. Recently, I did feel the desire of the community and Flink users for Python support. Stephan also pointed out in the

Re: [DISCUSS] Move flink-python to opt

Thanks for bringing up this DISCUSS Ufuk! Makes sense. +1 for doing this. Best, Jincheng Ufuk Celebi 于2019年2月25日周一 下午10:33写道： > Dear devs, > > what are your thoughts about moving flink-python (batch API) to opt > instead of having it in lib? The streaming counter part >

Re: [RESULT][VOTE] Clean up and reorganize the JIRA components

I agree with Robert from now. Best, Jincheng Robert Metzger 于2019年2月26日周二 下午7:03写道： > Thank you for the suggestion. > > Would this be "Runtime / State TTL" ? > > How about adding this once we really have collected enough tickets to > justify a separate component? > The number of components is

Re: [DISCUSS] Improve the flinkbot

ew= > review=☐☐☐☑ > review=☐☐☑☑ > review=☐☑☑☑ > review=✅ > > *Alternative 2:* > > review=description > > review=consensus > > review=architecture > > review=quality > > review=approved ✅ > > We could also add a ( ❓) emoji to alternative

Re: [ANNOUNCE] Flink 1.8 release branch has been cut

r driving this and cutting the new branch. > Looking forward to the release candidate :-) > > Best, Hequn > > On Mon, Feb 25, 2019 at 6:23 PM Kurt Young wrote: > > > Thanks Aljoscha! > > > > Best, > > Kurt > > > > > > On Mon, Feb 25

  1   2   3   4   >