Re: [ANNOUNCE] Apache Flink 1.8.1 released

Thanks for being the release manager and the great job! Cheers, Jark On Wed, 3 Jul 2019 at 10:16, Dian Fu wrote: > Awesome! Thanks a lot for being the release manager. Great job! @Jincheng > > Regards, > Dian > > 在 2019年7月3日，上午10:08，jincheng sun 写道： > > I've also tweeted about it from my twitt

Re: [DISCUSS]Support Upsert mode for Streaming Non-window FlatAggregate

Hi jingcheng, I agree with Kurt's point. As you said "the user must know the keys of the output of UDTAGG clearly". If I understand correctly, the key information is strongly relative to the UDTAGG implementation. Users may call `flatAggregate` on a UDTAGG instance with different keys which may re

Re: Flink 1.9 blink planner

Hi Kaka, Thanks for trying to use blink planner. We are working on bridging blink planner to the public API (i.e. TableEnvironment) and this is on a good way. Until then, we will remove blink's own TableEnvironment and use API's TableEnvironment and your problem will be fixed. Ideally, we can fin

Re: [VOTE] Migrate to sponsored Travis account

gt;>> > echo "" > > > >>> >>>> > echo "To trigger CI after setup, you will need > > > >>> ammend your > > > >>> >>>> last commit > > > >>> >

Re: [DISCUSS]Support Upsert mode for Streaming Non-window FlatAggregate

gt; > For example, take TopN again as an example. If the TopN table aggregate > function > outputs three columns(rankid, time, value), either rankid or rankid+time > could be > used as the key. Which one to be chosen is more likely to be decided by > the user > according to his bu

Re: [DISCUSS]Support Upsert mode for Streaming Non-window FlatAggregate

ys` approach becomes hang in > doubt. > > So, to avoid the unification problem, I think we can also use the approach > 3. It is more rigorous although less flexible compared to the `withKeys` > approach. > > Meanwhile, I will think more about the unification problem later. Maybe &g

Re: [ANNOUNCE] Rong Rong becomes a Flink committer

Congratulations Rong Rong! Welcome on board! On Thu, 11 Jul 2019 at 22:25, Fabian Hueske wrote: > Hi everyone, > > I'm very happy to announce that Rong Rong accepted the offer of the Flink > PMC to become a committer of the Flink project. > > Rong has been contributing to Flink for many years, m

Re: blink planner issue

Hi Kaka, Thanks for reporting this. We didn't cover integrate tests for connectors yet because of FLINK-13276. We will cover that after FLINK-13276 is fixed. The problem you raised might because we misused `LogicalType.equals` which will checks field names as well. I have created an issue (FLINK-

Re: blink planner issue

ical row type shouldn't break this behavior. > > > > kaka chen 于2019年7月16日周二 下午10:53写道： > > > > > Hi Jark, > > > > > > Thanks! > > > > > > Thanks, > > > Kaka Chen > > > > > > Jark Wu 于2019年7月16日周二 下午10:3

Re: Flink "allow lateness" for tables

Hi Ramya, Are you looking for "allow lateness" for tumbling window in Flink SQL? If yes, Flink SQL doesn't provide such things currently. However, blink planner (the new runner of Flink SQL) will support this maybe in the next release (v1.10). Actually, we already implemented it in blink planner

Re: [ANNOUNCE] Jiangjie (Becket) Qin has been added as a committer to the Flink project

Congratulations Becket! Well deserved. Cheers, Jark On Thu, 18 Jul 2019 at 15:56, Paul Lam wrote: > Congrats Becket! > > Best, > Paul Lam > > > 在 2019年7月18日，15:41，Robert Metzger 写道： > > > > Hi all, > > > > I'm excited to announce that Jiangjie (Becket) Qin just became a Flink > > committer! >

Re: 请问这些名词，在翻译 Glossary 时，有必要翻译成中文吗？

Hi highfei, Thanks for bringing up this discussion. I would suggest to move the discussion to the Glossary translation JIRA FLINK-13037 . Thanks, Jark On Fri, 19 Jul 2019 at 09:00, Zili Chen wrote: > Hi, > > 欢迎有 PR 后同步到这个 thread 上 :-) > >

Re: 请问这些名词，在翻译 Glossary 时，有必要翻译成中文吗？

Hi, Just find the Glossary translation PR is created [1]. Let's move the discussion there. [1]. https://github.com/apache/flink/pull/9173 On Fri, 19 Jul 2019 at 11:22, Jark Wu wrote: > Hi highfei, > > Thanks for bringing up this discussion. I would suggest to move the >

Re: [DISCUSS] A more restrictive JIRA workflow

A quick question, what should we do if a developer creates a JIRA issue and then create a pull request at once without assigning? Regards, Jark On Thu, 18 Jul 2019 at 18:50, Zili Chen wrote: > Checking the result, as a discovery, I found that one can > still file a JIRA with "blocker" priority

Re: flink-mapr-fs failed in travis

It seems that it is introduced by this commit: https://github.com/apache/flink/commit/5c36c650e6520d92191ce2da33f7dcae774319f6 Hi @Chesnay Schepler , do we need to add "-Punsafe-mapr-repo" to the ".travis.yml"? Best, Jark On Fri, 19 Jul 2019 at 10:58, JingsongLee wrote: > Hi everyone: > > flin

Re: flink-mapr-fs failed in travis

anv_watchdog.sh . > > > > On 19/07/2019 09:58, Chesnay Schepler wrote: > >> I did modify the .travis.yml do activate the unsafe-mapr-repo > >> profile; did I modified the wrong profile?... > >> > >> > >> On 19/07/2019 07:57, Jark Wu wrote: > &g

[DISCUSS] Setup a bui...@flink.apache.org mailing list for travis builds

Hi all, As far as I know, currently, email notifications of Travis builds for master branch are sent to the commit author when a build was just broken or still is broken. And there is no email notifications for CRON builds. Recently, we are suffering from compile errors for scala-2.12 and java-9

Re: Re: [ANNOUNCE] Zhijiang Wang has been added as a committer to the Flink project

Congratulations Zhijiang! On Tue, 23 Jul 2019 at 11:30, vino yang wrote: > Congratulations Zhijiang! > > Haibo Sun 于2019年7月23日周二 上午10:48写道： > > > Congrats, Zhejiang! > > > > > > Best, > > Haibo > > 在 2019-07-23 10:26:20，"Yun Tang" 写道： > > >Congratulations Zhijiang, well deserved. > > > > > >B

Re: [ANNOUNCE] Kete Young is now part of the Flink PMC

Congratulations Kurt! Well deserved. Cheers, Jark On Tue, 23 Jul 2019 at 17:43, LakeShen wrote: > Congratulations Kurt! > > Congxian Qiu 于2019年7月23日周二 下午5:37写道： > > > Congratulations Kurt! > > Best, > > Congxian > > > > > > Dian Fu 于2019年7月23日周二 下午5:36写道： > > > > > Congrats, Kurt! > > > > > >

Re: [DISCUSS] Setup a bui...@flink.apache.org mailing list for travis builds

day, July 22, 2019 9:44 > > > > >> To: dev > > > > >> Subject: Re: [DISCUSS] Setup a bui...@flink.apache.org mailing > list > > > > for travis builds > > > > >> > > > > >> +1. Sounds a good idea to me. > >

Re: [DISCUSS] Setup a bui...@flink.apache.org mailing list for travis builds

k. +1 for the proposal. > >> > > >> > Cheers, > >> > Till > >> > > >> >> On Tue, Jul 23, 2019 at 1:59 PM Hequn Cheng > >> wrote: > >> >> > >> >> Hi Jark, > >> >> &g

Re: [DISCUSS] Support computed column for Flink SQL

Hi Danny, Thanks for bringing this. I agree with Timo. We can have a thorough discussion once 1.9 release is published. And the computed column support & implementation might be good to be discussed with "table source and sink concept"[1]. Whatever, I left some my initial thoughts in the doc. Bes

Re: [DISCUSS] Setup a bui...@flink.apache.org mailing list for travis builds

have some progress. Thanks, Jark [1]: https://github.com/apache/flink/pull/9230 On Thu, 25 Jul 2019 at 22:59, Robert Metzger wrote: > 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 hel

Re: NoSuchMethodError: org.apache.calcite.tools.FrameworkConfig.getTraitDefs()

Hi Lakeshen, Thanks for trying out blink planner. First question, are you using blink-1.5.1 or flink-1.9-table-planner-blink ? We suggest to use the latter one because we don't maintain blink-1.5.1, you can try flink 1.9 instead. Best, Jark On Tue, 30 Jul 2019 at 17:02, LakeShen wrote: > Hi

Re: [VOTE] Publish the PyFlink into PyPI

+1 (non-binding) Cheers, Jark On Thu, 1 Aug 2019 at 17:45, Yu Li wrote: > +1 (non-binding) > > Thanks for driving this! > > Best Regards, > Yu > > > On Thu, 1 Aug 2019 at 11:41, Till Rohrmann wrote: > > > +1 > > > > Cheers, > > Till > > > > On Thu, Aug 1, 2019 at 10:39 AM vino yang wrote: > >

Re: [RESULT][VOTE] Migrate to sponsored Travis account

avis > >>>>>> >>>> > set +x > >>>>>> >>>> > echo > >>>>>> "-" > >>>>>> >>>> >

Re: [DISCUSS] CPU flame graph for a job vertex in web UI.

Hi David, The demo looks charming! I think it will definitely help a lot when performance tuning. A big +1 for this. I cc-ed Yadong who's one of the main contributors of the new Web UI. Maybe he can give some help on the front end. Regards, Jark On Fri, 2 Aug 2019 at 04:26, David Morávek wrote

Re: [DISCUSS][CODE STYLE] Usage of Java Optional

Hi Andrey, I have some concern on point (3) "even class fields as e.g. optional config options with implicit default values". Regarding to the Oracle's guide (4) "Optional should not be used for class fields". And IntelliJ IDEA also report warnings if a class field is Optional, because Optional i

Re: [DISCUSS][CODE STYLE] Usage of Java Optional

SerializableOptional. It would be sufficient. > > Best, > tison. > > > Jark Wu 于2019年8月2日周五 下午4:57写道： > > > Hi Andrey, > > > > I have some concern on point (3) "even class fields as e.g. optional > config > > options with implicit default val

Re: [RESULT][VOTE] Migrate to sponsored Travis account

Wow. That's great! Thanks Chesnay. On Fri, 2 Aug 2019 at 17:50, Chesnay Schepler wrote: > I'm currently modifying the cibot to do this automatically; should be > finished until Monday. > > On 02/08/2019 07:41, Jark Wu wrote: > > Hi Chesnay, > > > > Can w

Re: [ANNOUNCE] Hequn becomes a Flink committer

Congratulations Hequn! It's great to have you in the community! On Wed, 7 Aug 2019 at 21:00, Fabian Hueske wrote: > Congratulations Hequn! > > Am Mi., 7. Aug. 2019 um 14:50 Uhr schrieb Robert Metzger < > rmetz...@apache.org>: > >> Congratulations! >> >> On Wed, Aug 7, 2019 at 1:09 PM highfei2.

Re: [DISCUSS] Repository split

Hi, First of all, I agree with Dawid and David's point. I will share some experience on the repository split. We have been through it for Alibaba Blink, which is the most worthwhile project to learn from I think. We split Blink project into "blink-connectors" and "blink", but we didn't get much b

Re: Flink cannot recognized catalog set by registerCatalog.

I think we might need to improve the javadoc of tableEnv.registerTableSource/registerTableSink. Currently, the comment says "Registers an external TableSink with already configured field names and field types in this TableEnvironment's catalog." But, what catalog? The current one or default in-me

Re: [VOTE] Apache Flink Release 1.9.0, release candidate #2

Hi all, I just find an issue when testing connector DDLs against blink planner for rc2. This issue lead to the DDL doesn't work when containing timestamp/date/time type. I have created an issue FLINK-13699[1] and a pull request for this. IMO, this can be a blocker issue of 1.9 release. Because ti

Re: Flink cannot recognized catalog set by registerCatalog.

; “registerCatalog”, but it does not work in some cases ( like my cases ). > Do you think it’s feasible to unify this behaviors ? I think the document > is necessary, but a unify way to use tableEnv is also important. > > Thanks, > SImon > > On 08/13/2019 12:27，Jark Wu wrote： &

Re: [VOTE] Apache Flink Release 1.9.0, release candidate #2

er > > will be rather a preview feature than production ready. Hence it could > > still contain some bugs. My concern is that there might be still other > > issues which we'll discover bit by bit and could postpone the release > even > > further if we say Bli

Re: [VOTE] Flink Project Bylaws

+1 (non-binding) Best, Jark On Wed, 14 Aug 2019 at 09:22, Kurt Young wrote: > +1 (binding) > > Best, > Kurt > > > On Wed, Aug 14, 2019 at 1:34 AM Yun Tang wrote: > > > +1 (non-binding) > > > > But I have a minor question about "code change" action, for those > > "[hotfix]" github pull requests

Re: [VOTE] Apache Flink Release 1.9.0, release candidate #2

better to make these > examples available differently, maybe through Flink's ecosystem website or > maybe a new examples section in Flink's documentation. > > Cheers, > Till > > On Tue, Aug 13, 2019 at 9:43 AM Jark Wu wrote: > > > Hi Till, > > > > A

Re: Unbearably slow Table API time-windowed stream join with RocksDBStateBackend

Hi Xiao, Thanks for reporting this. You approach sounds good to me. But we have many similar problems in existing streaming sql operator implementations. So I think if State API / statebackend can provide a better state structure to handle this situation would be great. This is a similar problem

Re: [ANNOUNCE] Andrey Zagrebin becomes a Flink committer

Congratulations Andrey! Cheers, Jark On Thu, 15 Aug 2019 at 00:57, jincheng sun wrote: > Congrats Andrey! Very happy to have you onboard :) > > Best, Jincheng > > Yu Li 于2019年8月15日周四 上午12:06写道： > > > Congratulations Andrey! Well deserved! > > > > Best Regards, > > Yu > > > > > > On Wed, 14 Au

Re: [DISCUSS] FLIP-51: Rework of the Expression Design

Thanks Jingsong for starting the discussion. The general design of the FLIP looks good to me. +1 for the FLIP. It's time to get rid of the old Expression! Regarding to the function behavior, shall we also include new functions from blink planner (e.g. LISTAGG, REGEXP, TO_DATE, etc..) ? Best, Ja

Re: flink 1.9 DDL nested json derived

Hi Shengnan, Yes. Flink 1.9 supports nested json derived. You should declare the ROW type with nested schema explicitly. I tested a similar DDL against 1.9.0 RC2 and worked well. CREATE TABLE kafka_json_source ( rowtime VARCHAR, user_name VARCHAR, event ROW ) WITH ( 'connector.typ

Re: [VOTE] Apache Flink Release 1.9.0, release candidate #2

>>>>>>> > > > > >>>>>>> I did some testing on a Google Cloud Dataproc cluster (it > gives > > > you > > > > >>> a > > > > >>>>>>> managed YARN and Google Cloud Storage (GCS)

Re: [DISCUSS] Reducing build times

Thanks Chesnay for starting this discussion. +1 for #1, it might be the easiest way to get a significant speedup. If the only reason is for isolation. I think we can fix the static fields or global state used in Flink if possible. +1 for #2, and thanks Aleksey for the prototype. I think it's a go

Re: [VOTE] FLIP-51: Rework of the Expression Design

+1 from my side. Thanks Jingsong for driving this. Best, Jark On Thu, 15 Aug 2019 at 22:09, Timo Walther wrote: > +1 for this. > > Thanks, > Timo > > Am 15.08.19 um 15:57 schrieb JingsongLee: > > Hi Flink devs, > > > > I would like to start the voting for FLIP-51 Rework of the Expression > >

Re: [DISCUSS] FLIP-54: Evolve ConfigOption and Configuration

Thanks for starting this design Timo and Dawid, Improving ConfigOption has been hovering in my mind for a long time. We have seen the benefit when developing blink configurations and connector properties in 1.9 release. Thanks for bringing it up and make such a detailed design. I will leave my tho

Re: [VOTE] Apache Flink Release 1.9.0, release candidate #2

rformance regression using 1.9 compared > to > > > > 1.8. > > > > > > > > It's still not very clear why this regression happens. > > > > > > > > > > > > > > > > Best, > > > > > > > > Guowei > > > > > > >

Re: [VOTE] Apache Flink 1.9.0, release candidate #3

+1 (non-binding) - build the source release with Scala 2.12 and Scala 2.11 successfully - checked/verified signatures and hashes - checked that all POM files point to the same version - started a cluster, ran a SQL query to temporal join with kafka source and mysql jdbc table, and write results to

Re: CiBot Update

Great work! Thanks Chesnay! On Thu, 22 Aug 2019 at 15:42, Xintong Song wrote: > The re-triggering travis feature is so convenient. Thanks Chesnay~! > > Thank you~ > > Xintong Song > > > > On Thu, Aug 22, 2019 at 9:26 AM Stephan Ewen wrote: > > > Nice, thanks! > > > > On Thu, Aug 22, 2019 at 3

Re: [ANNOUNCE] Apache Flink 1.9.0 released

Congratulations! Thanks Gordon and Kurt for being the release manager and thanks a lot to all the contributors. Cheers, Jark On Thu, 22 Aug 2019 at 20:06, Oytun Tez wrote: > Congratulations team; thanks for the update, Gordon. > > --- > Oytun Tez > > *M O T A W O R D* > The World's Fastest Hu

Re: [DISCUSS] Use Java's Duration instead of Flink's Time

+1 to use Java's Duration instead of Flink's Time. Regarding to the Duration parsing, we have mentioned this in FLIP-54[1] to use `org.apache.flink.util.TimeUtils` for the parsing. Best, Jark [1]: https://docs.google.com/document/d/1IQ7nwXqmhCy900t2vQLEL3N2HIdMg-JO8vTzo1BtyKU/edit#heading=h.egdw

Re: [DISCUSS] Setup a bui...@flink.apache.org mailing list for travis builds

ttps://docs.travis-ci.com/user/notifications/#configuring-webhook-notifications [4]: https://docs.travis-ci.com/user/notifications/#configuring-email-notifications On Tue, 30 Jul 2019 at 18:35, Jark Wu wrote: > Hi all, > > Progress updates: > 1. the bui...@flink.apache.org can be

Re: [CODE-STYLE] Builder pattern

Hi Gyula, Thanks for bringing this. I think it would be nice if we have a common approach to create builder pattern. Currently, we have a lot of builders but with different tastes. > 1. Creating the builder objects: I prefer option a) too. It would be easier for users to get the builder instance

Re: [DISCUSS] Enhance Support for Multicast Communication Pattern

Hi all, Thanks Yun for bringing this topic. I missed this discussion because of the "multicast" title. After reading the design, if I understand correctly, it is proposing a custom event mach mechanism, i.e. broadcasting custom event. It is a orthogonality topic with multicasting. So I would sugge

Re: [VOTE] FLIP-54: Evolve ConfigOption and Configuration

+1 to the FLIP. Regards, Jark > 在 2019年8月27日，19:28，Timo Walther 写道： > > Hi everyone, > > thanks for the great feedback we have received for the draft of FLIP-54. The > discussion seems to have reached an agreement. Of course this doesn't mean > that we can't propose further improvements on

Re: [VOTE] FLIP-54: Evolve ConfigOption and Configuration

Hi Timo, The new changes looks good to me. +1 to the FLIP. Cheers, Jark On Wed, 28 Aug 2019 at 16:02, Timo Walther wrote: > Hi everyone, > > after some last minute changes yesterday, I would like to start a new > vote on FLIP-54. The discussion seems to have reached an agreement. Of > course

Re: [DISCUSS] Setup a bui...@flink.apache.org mailing list for travis builds

AM jincheng sun > wrote: > > > Great Job Jark :) > > Best, Jincheng > > > > Kurt Young 于2019年8月26日周一 下午6:38写道： > > > > > Thanks for the updates, Jark! I have subscribed the ML and everything > > > looks good now. > > > > > > Best

Re: [VOTE] FLIP-58: Flink Python User-Defined Function for Table API

+1 Thanks for the great work! On Fri, 30 Aug 2019 at 10:04, Xingbo Huang wrote: > Hi Dian, > > +1, > Thanks a lot for driving this. > > Best, > Xingbo > > 在 2019年8月30日，上午9:39，Wei Zhong 写道： > > > > Hi Dian, > > > > +1 non-binding > > Thanks for driving this! > > > > Best, Wei > > > >> 在 2019年8月

Re: [DISCUSS] Releasing Flink 1.8.2

Thanks Jincheng for bringing this up. +1 to the 1.8.2 release, because it already contains a couple of important fixes and it has been a long time since 1.8.1 came out. I'm willing to help the community as much as possible. I'm wondering if I can be the release manager of 1.8.2 or work with you to

Re: [DISCUSS] Releasing Flink 1.8.2

ngaFlinkRelease-Checklisttoproceedtothenextstep.1 > > > > Cheers, > > Jincheng > > > > Till Rohrmann 于2019年8月31日周六 上午12:59写道： > > > > > +1 for a 1.8.2 bug fix release. Thanks for kicking this discussion off > > > Jincheng. > > > > >

Re: [DISCUSS] FLIP-60: Restructure the Table API & SQL documentation

big +1 to the idea of restructuring the docs. We got a lot of complaints from users about the Table & SQL docs. In general, I think the new structure is very nice. Regarding to moving "User-defined Extensions" to corresponding broader topics, I would prefer current "User-defined Extensions". Beca

Re: Flink SQL - Support Computed Columns in DDL?

Hi Qi, The computed column is not fully supported in 1.9. We will start a design discussion in the dev mailing list soon. Please stay tuned! Btw, could you share with us what's the case why do you want to use computed column? Best, Jark On Tue, 3 Sep 2019 at 19:25, Danny Chan wrote: > Yeah, w

Re: [DISCUSS] Releasing Flink 1.8.2

> >>> Hi Jark, > > > > > >>> > > > > > >>> Glad to hear that you want to be the Release Manager of flink > > > 1.8.2. > > > > > >>> I believe that you will be a great RM, and I am very willing to > > &g

Re: [DISCUSS] Releasing Flink 1.8.2

ark! > > Kostas > > On Tue, Sep 3, 2019 at 4:19 PM Jark Wu wrote: > > > > Thanks Kostas for the quick fixing. > > > > However, I find that FLINK-13940 still target to 1.8.2 as a blocker. If I > > understand correctly, FLINK-13940 is aiming for a nicer and better &

Re: [DISCUSS] Releasing Flink 1.8.2

ion 1.8.3 in JIRA, could you please remark the > JIRAs(Such as FLINK-13689) which we do not want merge into the 1.8.2 > release :) > > You are right, I think FLINK-13586 is better to be contained in 1.8.2 > release! > > Thanks, > Jincheng > > > Jark Wu 于2019年9月4日周三

Re: [DISCUSS] FLIP-57 - Rework FunctionCatalog

Hi all, Regarding #1 temp function <> built-in function and naming. I'm fine with temp functions should precede built-in function and can override built-in functions (we already support to override built-in function in 1.9). If we don't allow the same name as a built-in function, I'm afraid we wil

Re: [VOTE] FLIP-62: Set default restart delay for FixedDelay- and FailureRateRestartStrategy to 1s

+1 Best, Jark > 在 2019年9月4日，19:43，David Morávek 写道： > > +1 > > On Wed, Sep 4, 2019 at 1:38 PM Till Rohrmann wrote: > >> +1 (binding) >> >> On Wed, Sep 4, 2019 at 12:43 PM Chesnay Schepler >> wrote: >> >>> +1 (binding) >>> >>> On 04/09/2019 11:18, JingsongLee wrote: +1 (non-binding)

Re: [DISCUSS] Support JSON functions in Flink SQL

Hi Forward, Thanks for bringing this discussion and preparing the nice design. I think it's nice to have the JSON functions in the next release. We have received some requirements for this feature. I can help to shepherd this JSON functions effort and will leave comments in the design doc in the

[DISCUSS] FLIP-66: Support time attribute in SQL DDL

Hi everyone, I would like to start discussion about how to support time attribute in SQL DDL. In Flink 1.9, we already introduced a basic SQL DDL to create a table. However, it doesn't support to define time attributes. This makes users can't apply window operations on the tables created by DDL wh

Re: [DISCUSS] Support notifyOnMaster for notifyCheckpointComplete

I think before we have such interface, maybe we can make task-0 to do the global finalize work. Best, Jark > 在 2019年9月6日，13:39，shimin yang 写道： > > Hi Jingsong, > > Big fan of this idea. We faced the same problem and resolved by adding a > distributed lock. It would be nice to have this fea

Is Flink documentation deployment script broken ?

Hi all, I merged several documentation pull requests[1][2][3] days ago. AFAIK, the documentation deployment is scheduled every day. However, I didn't see the changes are available in the Flink doc website[4] until now. The same to Till's PR[5] merged 3 days ago. Best, Jark [1]: https://github.c

Re: Is Flink documentation deployment script broken ?

Thanks Chesnay for reporting this. > 在 2019年9月6日，17:47，Chesnay Schepler 写道： > > The scripts are fine, but the buildbot slave is currently down. > > I've already opened a ticket with INFRA: > https://issues.apache.org/jira/browse/INFRA-18986 > > On 06/09/2019 11

[VOTE] Release 1.8.2, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 1.8.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1],

Re: [DISCUSS] Releasing Flink 1.8.2

I’m just running the last tests on FLINK-13586 on Travis and them I’m > merging. > > Best, > Aljoscha > > On 4. Sep 2019, at 07:37, Jark Wu wrote: > > Thanks for the work Jincheng! > > I have moved remaining major issues to 1.8.3 except FLINK-13586. > > Hi @Aljoscha

Re: [ANNOUNCE] Kostas Kloudas joins the Flink PMC

Congratulations Klou! > 在 2019年9月7日，00:21，zhijiang 写道： > > Congratulations Klou! > > Best, > Zhijiang > -- > From:Zhu Zhu > Send Time:2019年9月6日(星期五) 17:19 > To:dev > Subject:Re: [ANNOUNCE] Kostas Kloudas joins the Flink PMC > >

Re: [DISCUSS] Features for Apache Flink 1.10

Thanks Gary for kicking off the discussion for 1.10 release. +1 for Gary and Yu as release managers. Thank you for you effort. Best, Jark > 在 2019年9月7日，00:52，zhijiang 写道： > > Hi Gary, > > Thanks for kicking off the features for next release 1.10. I am very > supportive of you and Yu Li to

Re: [DISCUSS] FLIP-66: Support time attribute in SQL DDL

efinitely an import > feature > >> for the SQL, especially the DDL users. > >> > >> I would spend some time to review this design doc, really thanks. > >> > >> Best, > >> Danny Chan > >> 在 2019年9月6日 +0800 AM11:19，Jark Wu ，写道： > >

Re: [ANNOUNCE] Zili Chen becomes a Flink committer

Congratulations Zili! Best, Jark On Wed, 11 Sep 2019 at 23:06, wrote: > Congratulations, Zili. > > > > Best, > > Xingcan > > > > *From:* SHI Xiaogang > *Sent:* Wednesday, September 11, 2019 7:43 AM > *To:* Guowei Ma > *Cc:* Fabian Hueske ; Biao Liu ; > Oytun Tez ; bupt_ljy ; dev < > dev@flink

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

9年9月9日，下午2:28，jincheng sun 写道： > > > > > > > > +1 (binding) > > > > > > > > - checked signatures [SUCCESS] > > > > - built from source without tests [SUCCESS] > > > > - ran some tests in IDE [SUCCESS] > > > > - sta

[RESULT] [VOTE] Release 1.8.2, release candidate #1

I'm happy to announce that we have unanimously approved this release. There are 5 approving votes, 3 of which are binding: * jincheng (binding) * Kurt (binding) * Till (binding) * Dian * Jark There are no disapproving votes. Thanks everyone!

Re: Blink Planner HBaseUpsertTableSink Exception

Hi Lake, This is not a problem of HBaseUpsertTableSink. This is because the query loses primary key (e.g. concat(key1, key2) will lose the primary key information [key1, key2] currently.), but the validation of inserting checks the upsert query should have a primary key. That’s why the exception i

[ANNOUNCE] Apache Flink 1.8.2 released

Hi, The Apache Flink community is very happy to announce the release of Apache Flink 1.8.2, which is the second bugfix release for the Apache Flink 1.8 series. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streami

Re: [DISCUSS] FLIP-57 - Rework FunctionCatalog

Hi, +1 to strive for reaching consensus on the remaining topics. We are close to the truth. It will waste a lot of time if we resume the topic some time later. +1 to “1-part/override” and I’m also fine with Timo’s “cat.db.fun” way to override a catalog function. I’m not sure about “system.sy

Re: Retention policy | Memory management.

Hi, The Job1 is a simple ETL job and doesn’t consume much state size (only Kafka offset), so it should work well. The Job2 is an unbounded join which will put the two input stream data into state in Join operator. As the input stream is unlimited and 100GB per day as you described, if you are

Re: [DISCUSS] FLIP-66: Support time attribute in SQL DDL

, I think it's time > to > convert this design to a cwiki flip page and start voting process. > > Best, > Kurt > > > On Mon, Sep 9, 2019 at 7:46 PM Jark Wu wrote: > > > Hi all, > > > > Thanks all for so much feedbacks received in the doc so far. >

[VOTE] FLIP-66: Support Time Attribute in SQL DDL

Hi all, I would like to start the vote for FLIP-66 [1], which is discussed and reached a consensus in the discussion thread[2]. The vote will be open for at least 72 hours. I'll try to close it after Sep. 24 08:00 UTC, unless there is an objection or not enough votes. Thanks, Jark [1]: https://

Re: [DISCUSS] FLIP-57 - Rework FunctionCatalog

> catalog function. > > > > > (Resolution for partially or fully qualified function reference is: > > > temp > > > > > functions -> persistent functions.) > > > > > > > > > > 3. In addition to #1, suppor

Re: [DISCUSS] FLIP-64: Support for Temporary Objects in Table module

Thanks Dawid for the design doc. In general, I’m +1 to the FLIP. +1 to the single-string and parse way to express object path. +1 to deprecate registerTableSink & registerTableSource. But I would suggest to provide an easy way to register a custom source/sink before we drop them (this is an

Re: [DISCUSS] FLIP-316: Introduce SQL Driver

Hi Paul, Thanks for starting this discussion. I like the proposal! This is a frequently requested feature! I agree with Shengkai that ExecNodeGraph as the submission object is a better idea than SQL file. To be more specific, it should be JsonPlanGraph or CompiledPlan which is the serializable re

Re: [DISCUSS] FLIP-315: Support Operator Fusion Codegen for Flink SQL

Hi Ron, Thanks a lot for the great proposal. The FLIP looks good to me in general. It looks like not an easy work but the performance sounds promising. So I think it's worth doing. Besides, if there is a complete test graph with all TPC-DS queries, the effect of this FLIP will be more intuitive.

Re: [DISCUSS] FLIP 295: Support persistence of Catalog configuration and asynchronous registration

Hi Feng, This is a useful FLIP. Thanks for starting this discussion. The current design looks pretty good to me. I just have some minor comments. 1. How to register the CatalogStore for Table API? I think the CatalogStore should be immutable once TableEnv is created. Otherwise, there might be som

Re: [DISCUSS] Hive dialect shouldn't fall back to Flink's default dialect

+1, I think this can make the grammar more clear. Please remember to add a release note once the issue is finished. Best, Jark On Thu, 1 Jun 2023 at 11:28, yuxia wrote: > Hi, Jingsong. It's hard to provide an option regarding to the fact that we > also want to decouple Hive with flink planner.

[DISCUSS] Update Flink Roadmap

Hi all, Martijn and I would like to initiate a discussion on the Flink roadmap, which should cover the project's long-term roadmap and the regular update mechanism. Xintong has already started a discussion about Flink 2.0 planning. One of the points raised in that discussion is that we should hav

Re: [DISCUSS] Update Flink Roadmap

gt; > Best regards, > Jing > > On Thu, Jun 1, 2023 at 3:31 PM Jark Wu wrote: > > > Hi all, > > > > Martijn and I would like to initiate a discussion on the Flink roadmap, > > which should cover the project's long-term roadmap and the regular update >

Re: [DISCUSS] FLIP-316: Introduce SQL Driver

aphs. > > > >> Regarding "K8S doesn't support shipping multiple jars", is that true? > Is it > >> possible to support it? > > > > Yes, K8s doesn’t distribute any files. It’s the users’ responsibility to > make > > sure the resources are ac

Re: [DISCUSS] FLIP 295: Support persistence of Catalog configuration and asynchronous registration

t; > interface, the CatalogStoreFactory should not have a default method > but > > > an > > > > interface method. I have already modified the interface. > > > > > > > > > 3. Please mention the alternative API in Javadoc for the > > >

Re: [VOTE] Release flink-connector-pulsar 3.0.1, release candidate #1

+1 (binding) - Build and compile the source code locally: *OK* - Verified signatures and hashes: *OK* - Checked no missing artifacts in the staging area: *OK* - Reviewed the website release PR: *OK* Best, Jark On Thu, 1 Jun 2023 at 07:30, Jing Ge wrote: > +1(non-binding) > > - verified sign >

Re: [VOTE] FLIP-315: Support Operator Fusion Codegen for Flink SQL

+1 (binding) Best, Jark > 2023年6月7日 14:20，liu ron 写道： > > Hi everyone, > > Thanks for all the feedback about FLIP-315: Support Operator Fusion Codegen > for Flink SQL[1]. > [2] is the discussion thread. > > I'd like to start a vote for it. The vote will be open for at least 72 > hours (until

Re: [DISCUSS] FLIP-305: Support atomic for CREATE TABLE AS SELECT(CTAS) statement

Thank you for the great work, Mang! The updated proposal looks good to me. Best, Jark > 2023年6月8日 11:49，Jingsong Li 写道： > > Thanks Mang for updating! > > Looks good to me! > > Best, > Jingsong > > On Wed, Jun 7, 2023 at 2:31 PM Mang Zhang wrote: >> >> Hi Jingsong, >> >>> I have some doub

Re: [DISCUSS] FLIP-311: Support Call Stored Procedure

Thank you for the proposal, yuxia! The FLIP looks good to me. Best, Jark > 2023年6月8日 11:39，yuxia 写道： > > Hi, all. > Thanks everyone for the valuable input. If there are are no further concerns > about this FLIP[1], I would like to start voting next monday (6/12). > > [1] > https://cwiki.apa

  1   2   3   4   5   6   7   8   9   10   >