Re: [VOTE] Release flink-shaded 17.0, release candidate #1

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - checked release notes - reviewed the web PR - filed issue FLINK-31994[1] to update the copyright year, not a blocker Best, Leonard [1] https://issues.apache.org/jira/browse/

[jira] [Created] (FLINK-31994) Update copyright in NOTICE files of flink-shaded

2023-05-03 Thread Leonard Xu (Jira)
Leonard Xu created FLINK-31994: -- Summary: Update copyright in NOTICE files of flink-shaded Key: FLINK-31994 URL: https://issues.apache.org/jira/browse/FLINK-31994 Project: Flink Issue Type: Bug

Re: [VOTE] Release flink-connector-cassandra v3.1.0, release candidate #1

2023-05-03 Thread Leonard Xu
-1 (binding) as the blocker issue FLINK-31927[1] found - Reviewed the PR [2] and left one comment that the linked issue is incorrect. Best, Leonard [1] https://issues.apache.org/jira/browse/FLINK-31927 [2] https://github.com/apache/flink-connector-cassandra/pull/13 > 2023年5月3日 下午5:26,Etienne

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

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - checked release notes - checked the contents of maven repo - reviewed the web PR Best, Leonard > 2023年4月21日 上午1:07,Ahmed Hamdy 写道: > > + (non-binding) > - Verified signat

Re: [VOTE] Release flink-connector-gcp-pubsub v3.0.1, release candidate #1

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - checked release notes - reviewed the web PR Best, Leonard > 2023年4月20日 上午3:17,Martijn Visser 写道: > > +1 (binding) > > - Validated hashes > - Verified signature > - Verif

Re: [VOTE] Release flink-connector-jdbc v3.1.0, release candidate #1

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - checked release notes - reviewed the web PR - found the JDBC docs contains a valid link, reopened FLINK-31759[1] to fix it, not a blocker Best, Leonard [1]https://issues.ap

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

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - checked release notes - reviewed the web PR Best, Leonard > 2023年5月2日 下午3:14,Khanh Vu 写道: > > +1 (non-binding) > > - Verified sha512 checksum matches file archive. > - V

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

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - checked release notes - reviewed the web PR and left minor comment Best, Leonard > 2023年4月24日 下午5:13,Danny Cranmer 写道: > > +1 (binding) > > - Release notes look ok > - Ve

Re: [VOTE] Release flink-connector-rabbitmq v3.0.1, release candidate #1

2023-05-03 Thread Leonard Xu
+1 (binding) - built from source code succeeded - verified signatures - verified hashsums - checked Github release tag - reviewed the web PR Best, Leonard > 2023年4月20日 上午3:29,Martijn Visser 写道: > > +1 (binding) > > - Validated hashes > - Verified signature > - Verified that no binaries ex

Re: Permission issue : Flink Code Push

2023-05-03 Thread Zhanghao Chen
Hi Archit, The procedure is: 1. Fork the flink repo 2. Implement your change and push to your fork 3. Create a pull request from your fork 4. Wait for reviews You can refer to https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-wi

Permission issue : Flink Code Push

2023-05-03 Thread Archit Goyal
Hi, I am new to the Flink community and am working on the FLINK-12869. I have a PR to be uploaded but I am unable to do push. I get a 403 error: argoyal@argoyal flink % git push --set-upstream origin YarnAcl remote: Permission to apache/flink.g

[jira] [Created] (FLINK-31993) Introduce JobMaster FailureEnricher configuration

2023-05-03 Thread Panagiotis Garefalakis (Jira)
Panagiotis Garefalakis created FLINK-31993: -- Summary: Introduce JobMaster FailureEnricher configuration Key: FLINK-31993 URL: https://issues.apache.org/jira/browse/FLINK-31993 Project: Flink

Re: [DISCUSS] SqlClient gateway mode: support for URLs

2023-05-03 Thread Thomas Weise
Hi Alex, Thanks for the investigation and for the ideas on how to improve the SQL gateway REST client. I think the solution could come in 2 parts. Near term the existing client can be patched to support URL mapping and HTTPS based on a standard URL. If I understand your proposal correctly, that c

[jira] [Created] (FLINK-31992) FlinkKafkaConsumer API is suggested as part of documentation, when that API is deprecated for that flink version

2023-05-03 Thread Sandesh Mendan (Jira)
Sandesh Mendan created FLINK-31992: -- Summary: FlinkKafkaConsumer API is suggested as part of documentation, when that API is deprecated for that flink version Key: FLINK-31992 URL: https://issues.apache.org/jira/

Re: [DISCUSS] SqlClient gateway mode: support for URLs

2023-05-03 Thread Alexander Fedulov
CC'ing some people who worked on the original implementation - curious to hear your thoughts. Alex On Fri, 28 Apr 2023 at 14:41, Alexander Fedulov wrote: > I would like to discuss the current implementation of the SQL Gateway > support in SQL Cli Client and how it can be improved. > > 1) *hosna

[jira] [Created] (FLINK-31991) Update Autoscaler doc to reflect the changes brought by the new source scaling logic

2023-05-03 Thread Zhanghao Chen (Jira)
Zhanghao Chen created FLINK-31991: - Summary: Update Autoscaler doc to reflect the changes brought by the new source scaling logic Key: FLINK-31991 URL: https://issues.apache.org/jira/browse/FLINK-31991

Re: [VOTE] Release flink-connector-cassandra v3.1.0, release candidate #1

2023-05-03 Thread Etienne Chauchot
Hi all, @Danny, I just submitted the fix PR to unblock the release: https://github.com/apache/flink-connector-cassandra/pull/13 Best Etienne Le 02/05/2023 à 14:52, Danny Cranmer a écrit : Thanks for reporting this issue Etienne. Why was it not detected by the unit/integration tests? Can we

[jira] [Created] (FLINK-31990) Use Flink Configuration to specify KDS Source configuration object

2023-05-03 Thread Hong Liang Teoh (Jira)
Hong Liang Teoh created FLINK-31990: --- Summary: Use Flink Configuration to specify KDS Source configuration object Key: FLINK-31990 URL: https://issues.apache.org/jira/browse/FLINK-31990 Project: Fli

[jira] [Created] (FLINK-31989) Update documentation

2023-05-03 Thread Hong Liang Teoh (Jira)
Hong Liang Teoh created FLINK-31989: --- Summary: Update documentation Key: FLINK-31989 URL: https://issues.apache.org/jira/browse/FLINK-31989 Project: Flink Issue Type: Sub-task R

[jira] [Created] (FLINK-31988) Implement Python wrapper for new KDS source

2023-05-03 Thread Hong Liang Teoh (Jira)
Hong Liang Teoh created FLINK-31988: --- Summary: Implement Python wrapper for new KDS source Key: FLINK-31988 URL: https://issues.apache.org/jira/browse/FLINK-31988 Project: Flink Issue Type:

[jira] [Created] (FLINK-31987) Implement Table API support

2023-05-03 Thread Hong Liang Teoh (Jira)
Hong Liang Teoh created FLINK-31987: --- Summary: Implement Table API support Key: FLINK-31987 URL: https://issues.apache.org/jira/browse/FLINK-31987 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-31986) Implement Integration test for FLIP-27 DataStreams API

2023-05-03 Thread Hong Liang Teoh (Jira)
Hong Liang Teoh created FLINK-31986: --- Summary: Implement Integration test for FLIP-27 DataStreams API Key: FLINK-31986 URL: https://issues.apache.org/jira/browse/FLINK-31986 Project: Flink

Re: [DISCUSS] Planning Flink 2.0

2023-05-03 Thread Matthias Pohl
Hi everyone, I'm jumping in a bit late due to holidays. Generally, I agree with all the things that were shared in this thread. It would be great to see Flink 2.0 happening (especially in terms of the Java 17 support and the removal of code). I would prefer having a major release that focuses enti