[jira] [Created] (FLINK-26627) Allow user to config the init/max wait time in the ExponentialWaitStrategy of job submission

2022-03-13 Thread Yangze Guo (Jira)
Yangze Guo created FLINK-26627: -- Summary: Allow user to config the init/max wait time in the ExponentialWaitStrategy of job submission Key: FLINK-26627 URL: https://issues.apache.org/jira/browse/FLINK-26627

[jira] [Created] (FLINK-26626) Add Estimator and Transformer of StandardScaler in FlinkML

2022-03-13 Thread Zhipeng Zhang (Jira)
Zhipeng Zhang created FLINK-26626: - Summary: Add Estimator and Transformer of StandardScaler in FlinkML Key: FLINK-26626 URL: https://issues.apache.org/jira/browse/FLINK-26626 Project: Flink

[jira] [Created] (FLINK-26625) KinesisFirehoseSinkITCase failed on azure due to Could not find a valid Docker environment

2022-03-13 Thread Yun Gao (Jira)
Yun Gao created FLINK-26625: --- Summary: KinesisFirehoseSinkITCase failed on azure due to Could not find a valid Docker environment Key: FLINK-26625 URL: https://issues.apache.org/jira/browse/FLINK-26625 Proj

[jira] [Created] (FLINK-26624) Running HA (hashmap, async) end-to-end test failed on azure due to unable to find master logs

2022-03-13 Thread Yun Gao (Jira)
Yun Gao created FLINK-26624: --- Summary: Running HA (hashmap, async) end-to-end test failed on azure due to unable to find master logs Key: FLINK-26624 URL: https://issues.apache.org/jira/browse/FLINK-26624 P

[jira] [Created] (FLINK-26623) BlobsCleanupITCase failed on azure

2022-03-13 Thread Yun Gao (Jira)
Yun Gao created FLINK-26623: --- Summary: BlobsCleanupITCase failed on azure Key: FLINK-26623 URL: https://issues.apache.org/jira/browse/FLINK-26623 Project: Flink Issue Type: Bug Components

[jira] [Created] (FLINK-26622) Azure failed due to Connection timed out

2022-03-13 Thread Yun Gao (Jira)
Yun Gao created FLINK-26622: --- Summary: Azure failed due to Connection timed out Key: FLINK-26622 URL: https://issues.apache.org/jira/browse/FLINK-26622 Project: Flink Issue Type: Bug Com

Re: [DISCUSS] Preview release for Flink Kubernetes Operator

2022-03-13 Thread Biao Geng
Hi there, It is exciting to see the discussion of the release timeline! I agree that the end of March is a proper date. To make others easier get involved in this discussion, I think we may need to provide a more straightforward feature list for the preview release. The "Initial Feature Set" in FL

[jira] [Created] (FLINK-26621) flink-tests failed on azure due to Error occurred in starting fork

2022-03-13 Thread Yun Gao (Jira)
Yun Gao created FLINK-26621: --- Summary: flink-tests failed on azure due to Error occurred in starting fork Key: FLINK-26621 URL: https://issues.apache.org/jira/browse/FLINK-26621 Project: Flink Iss

Re: [DISCUSS] Preview release for Flink Kubernetes Operator

2022-03-13 Thread Gyula Fóra
@Konstantin: Yes I completely agree that for this release the API (CRD) should be marked experimental! I have opened a ticket to track this: https://issues.apache.org/jira/browse/FLINK-26620 @Yang Wang : I think we still have plenty of time to work on features like the session job before the rele

[jira] [Created] (FLINK-26620) Mark CRD classes experimental

2022-03-13 Thread Gyula Fora (Jira)
Gyula Fora created FLINK-26620: -- Summary: Mark CRD classes experimental Key: FLINK-26620 URL: https://issues.apache.org/jira/browse/FLINK-26620 Project: Flink Issue Type: Sub-task Comp

Re: [DISCUSS] Preview release for Flink Kubernetes Operator

2022-03-13 Thread Konstantin Knauf
Hi everyone, can we mark all the APIs as experimental/alpha so that it is clear that these can be broken in future releases for now? I think this would be very important given the early stage of the project. We want to be able to address shortcomings without worrying too much about backwards compa