[jira] [Created] (FLINK-12117) CassandraConnectorITCase fails on Java 9

Chesnay Schepler created FLINK-12117: Summary: CassandraConnectorITCase fails on Java 9 Key: FLINK-12117 URL: https://issues.apache.org/jira/browse/FLINK-12117 Project: Flink Issue Type:

[jira] [Created] (FLINK-12118) Documentation in left navigation is not in step with its content

Yu Haidong created FLINK-12118: -- Summary: Documentation in left navigation is not in step with its content Key: FLINK-12118 URL: https://issues.apache.org/jira/browse/FLINK-12118 Project: Flink

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

+1 We'll have to comb through JIRA again as I already found a number of tickets that were marked as fixed for 1.8.1, but are included in this RC. On 05/04/2019 07:10, Rong Rong wrote: +1 (non-binding) * Verified checksums and GPG files matches release files * Verified that the source archive

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

Went through JIRA and update the versions. On 05/04/2019 13:57, Chesnay Schepler wrote: +1 We'll have to comb through JIRA again as I already found a number of tickets that were marked as fixed for 1.8.1, but are included in this RC. On 05/04/2019 07:10, Rong Rong wrote: +1 (non-binding) *

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

Hi Thomas, Thanks for your quick reply. I will share my thoughts further. :) 1. Without the support of the User-defined function, the Python Table API can do a lot of things: (Of course, we need to support UDF on the Python Table API.） Do you have use cases where the Python table API can be appli

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

One more thing It's better to mention that Flink table API is a superset of Flink SQL, such as: - AddColumns/DropColums/RenameColumns, the detail can be found in Google doc - Interactive Pr

Re: [DISCUSS] Drop Elasticssearch 1 connector

+1 for dropping elasticsearch 1 connector. On Wed, Apr 3, 2019 at 5:10 AM Chesnay Schepler wrote: > Hello everyone, > > I'm proposing to remove the connector for elasticsearch 1. > > The connector is used significantly less than more recent versions (2&5 > are downloaded 4-5x more), and hasn't s

[jira] [Created] (FLINK-12119) Add OWASP Dependency Check to Flink Build

Konstantin Knauf created FLINK-12119: Summary: Add OWASP Dependency Check to Flink Build Key: FLINK-12119 URL: https://issues.apache.org/jira/browse/FLINK-12119 Project: Flink Issue Type:

[DISCUSS] Apache Flink at Season of Docs

Hello everyone, TL;DR If you need some improvements for Flink documentation, apply to Season of Docs before April 23rd. Background: Season of Docs is like Google Summer of Code, but for documentation. Projects write ideas on how they would like to improve their documentation, then if they are ac

Re: [DISCUSS] Drop Elasticssearch 1 connector

+1 to drop it Previously released versions are still available and compatible with newer Flink versions anyways. On Fri, Apr 5, 2019 at 2:12 PM Bowen Li wrote: > +1 for dropping elasticsearch 1 connector. > > On Wed, Apr 3, 2019 at 5:10 AM Chesnay Schepler > wrote: > >> Hello everyone, >> >> I

Re: [Discuss] Semantics of event time for state TTL

Hi Andrey, I agree with Elias. This would be the most natural behavior. I wouldn't add additional slightly different notions of time to Flink. As I can also see a use case for the combination * Timestamp stored: Event timestamp * Timestamp to check expiration: Processing Time we could (maybe in

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

Thanks, Chesnay! I had that tab open already and was prepared to do it but it’s good you also thought about it. :-) What about these three issues, though: https://issues.apache.org/jira/issues/?filter=12334772&jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.8.1%20and%20resolution%20!%3D%20

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

Ah, the first two are not on 1.8.0-rc5, but FLINK-11855 is. > On 6. Apr 2019, at 08:23, Aljoscha Krettek wrote: > > Thanks, Chesnay! I had that tab open already and was prepared to do it but > it’s good you also thought about it. :-) What about these three issues, > though: > https://issues.a