re: About flink 1.3.0 release packages.

Hi Ted: When I choose the Flink 1.2.1 version, I click the binaries, it is direct to http://archive.apache.org/dist/flink/flink-1.2.1/. It is ok. The Flink 1.3.0 now is different from other versions. How to choose the mirror? Thanks! -邮件原件- 发件人: Ted Yu

Re: About flink 1.3.0 release packages.

From #2, you need to choose a mirror site. What you have downloaded should be an html page. > On Jun 7, 2017, at 8:48 PM, Zhangrucong wrote: > > Hi Ted: > 1、I use the link https://flink.apache.org/downloads.html > 2、In this web, I choose the Latest stable

re: About flink 1.3.0 release packages.

Sorry, Ted. I put the images in attachments, can you see it? We want to download the binaries and source code of flink 1.3.0 release from https://flink.apache.org/downloads.html. I use the link which is showed in image of binary_download_link.png But the package size of binary and source code

Re: About flink 1.3.0 release packages.

Did you embed images ? The images didn't come thru. Consider use third party site for images. Thanks On Wed, Jun 7, 2017 at 8:05 PM, Zhangrucong wrote: > Hi: > >We want to download the binaries and source code of flink 1.3.0 release > from

Re: Update Netty version

Hi I found ticket in jira: https://issues.apache.org/jira/browse/FLINK-3952 For update to latest 4.0 I can create separate ticket and pull request in nearest 2 day. (I test in my env and all work correctly) Update on 4.1 not so easy: 1) we use tv.cntt:netty-router:jar:1.10 for rest endpoints 2)

Re: Update Netty version

Hi Alexey, Are you looking to create pull requests for upgrading Netty 4.0 and/or 4.1? Greg On Thu, May 18, 2017 at 4:41 AM, Alexey Demin wrote: > Hi > > Problem not directly in flink, but it you use flink with beam then in > classpath you have original netty 4.0.27 from

[jira] [Created] (FLINK-6866) ClosureCleaner.clean fails for scala's JavaConverters wrapper classes

SmedbergM created FLINK-6866: Summary: ClosureCleaner.clean fails for scala's JavaConverters wrapper classes Key: FLINK-6866 URL: https://issues.apache.org/jira/browse/FLINK-6866 Project: Flink

FlinkML on slack

Hi all, We took the initiative to create the organization for FlinkML on slack (thnx Eron). There is now a channel for model-serving . Another is coming for flink-jpmml. You are invited to join the channels and

Re: [DISCUSS] TravisCI auto cancellation

I agree, it's useful for pull requests, but in the master it easily leads to multiple commits in a row not being tests. Most recent builds are marked as failed because they were canceled... On 07.06.2017 18:41, Robert Metzger wrote: I think auto cancellation is also enabled for branch builds.

Re: [DISCUSS] TravisCI auto cancellation

I think auto cancellation is also enabled for branch builds. I think this is pretty bad to find out which commit introduced a build instability. I'll contact INFRA to check this again. On Wed, Mar 29, 2017 at 3:33 PM, Greg Hogan wrote: > Wow, that was a quick response that

Re: [DISCUSS] Release Apache Flink 1.3.1

I would also like to raise another potential blocker: it’s currently not easily possible for users to start a job in local mode in the IDE and to then interact with that cluster, say for experimenting with queryable state. At least one user walked into this problem already with the 1.3.0 RC:

[jira] [Created] (FLINK-6865) Expand checkstyle docs to include import in intellij

Chesnay Schepler created FLINK-6865: --- Summary: Expand checkstyle docs to include import in intellij Key: FLINK-6865 URL: https://issues.apache.org/jira/browse/FLINK-6865 Project: Flink

[jira] [Created] (FLINK-6864) Remove confusing "invalid POJO type" messages from TypeExtractor

Tzu-Li (Gordon) Tai created FLINK-6864: -- Summary: Remove confusing "invalid POJO type" messages from TypeExtractor Key: FLINK-6864 URL: https://issues.apache.org/jira/browse/FLINK-6864 Project:

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

Thanks Dian and Jark for this proposal! As you wrote, Till and I (and Kostas) have been thinking about this for some time but haven't had time to work on this feature. I think it would be a great addition and value add for Flink's SQL support and Table API. I read the proposal and think it is

[jira] [Created] (FLINK-6863) Fully separate streaming examples

Chesnay Schepler created FLINK-6863: --- Summary: Fully separate streaming examples Key: FLINK-6863 URL: https://issues.apache.org/jira/browse/FLINK-6863 Project: Flink Issue Type:

[jira] [Created] (FLINK-6862) Tumble window rowtime not resolve at logic plan validation

Mark You created FLINK-6862: --- Summary: Tumble window rowtime not resolve at logic plan validation Key: FLINK-6862 URL: https://issues.apache.org/jira/browse/FLINK-6862 Project: Flink Issue Type:

Re: [DISCUSS] Release Apache Flink 1.3.1

>From the list [1], not many of the JIRAs have been fixed. I think it would be nice to put the RC for 1.3.1 out this week, given that multiple users have complained about some issues in the 1.3.0 release. [1] https://issues.apache.org/jira/issues/?jql=labels%20%3D%20flink-rel-1.3.1-blockers On

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

Thanks a lot for opening the discussion! This is a really interesting idea that has been in our heads since the first implementation of the CEP library. A big +1 for moving forward with this. And as for the design document, I will definitely have a look and comment there. Kostas > On Jun 7,

[DISCUSS] Removal of twitter-inputformat

Hello, I'm proposing to remove the Twitter-InputFormat in FLINK-6710 , with an open PR you can find here . The PR currently has a +1 from Robert, but Timo raised some concerns saying that it is useful

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

Sorry, I forgot to cc you guys @Fabian, @Timo, @Till, @Kostas 2017-06-07 15:42 GMT+08:00 Jark Wu : > Hi devs, > > Dian and me and our teammates have investigated this for a long time. We > think consolidating Flink SQL and CEP is an exciting thing for Flink. It'll > make SQL

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

Hi devs, Dian and me and our teammates have investigated this for a long time. We think consolidating Flink SQL and CEP is an exciting thing for Flink. It'll make SQL more powerful and give users the ability to easily and quickly build CEP applications. And I find Flink community has also talked