Apply for contributing to Apache Flink

HiGuys, I want to contribute to ApacheFlink.Would you please give me the permission as a contributor?My JIRA ID is hechao. | | hechao | | 13250818...@163.com | 签名由网易邮箱大师定制

Re: Apply for contributing to Apache Flink

Hi hechao Welcome to the Flink community You no longer need contributor permissions. You can simply create a JIRA ticket and ask to be assigned to it in order to start working. Please also take a look at the Flink's contribution guidelines [1] for more information. [1] https://flink.apache.org/c

Re: [DISCUSS] FLIP-85: Delayed Job Graph Generation

Hi Peter, I think we need to reconsider tison's suggestion seriously. After FLIP-73, the deployJobCluster has beenmoved into `JobClusterExecutor#execute`. It should not be perceived for `CliFrontend`. That means the user program will *ALWAYS* be executed on client side. This is the by design behav

[jira] [Created] (FLINK-15391) DATE and TIMESTAMP partition columns don't work

Rui Li created FLINK-15391: -- Summary: DATE and TIMESTAMP partition columns don't work Key: FLINK-15391 URL: https://issues.apache.org/jira/browse/FLINK-15391 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-15392) SqlClient

liupengcheng created FLINK-15392: Summary: SqlClient Key: FLINK-15392 URL: https://issues.apache.org/jira/browse/FLINK-15392 Project: Flink Issue Type: Bug Reporter: liupengcheng

[jira] [Created] (FLINK-15393) Change 'ReturnExpiredIfNotCleanedUp' to 'NeverReturnExpired' in JoinRecordStateViews#createTtlConfig

hailong wang created FLINK-15393: Summary: Change 'ReturnExpiredIfNotCleanedUp' to 'NeverReturnExpired' in JoinRecordStateViews#createTtlConfig Key: FLINK-15393 URL: https://issues.apache.org/jira/browse/FLINK-1

[jira] [Created] (FLINK-15394) in yarn mode, jobmanager fails to start in case of rest.port conflict.

watters.wang created FLINK-15394: Summary: in yarn mode, jobmanager fails to start in case of rest.port conflict. Key: FLINK-15394 URL: https://issues.apache.org/jira/browse/FLINK-15394 Project: Flink

Flink 1.9 SQL Kafka Connector，Json format，how to deal with not json message?

Hi community,when I write the flink ddl sql like this: CREATE TABLE kafka_src ( id varchar, a varchar, b TIMESTAMP, c TIMESTAMP ) with ( ... 'format.type' = 'json', 'format.property-version' = '1', 'format.derive-schema' = 'true', 'update-mode' = 'append' ); If the me

[jira] [Created] (FLINK-15395) No API for execute insert into statement

Jeff Zhang created FLINK-15395: -- Summary: No API for execute insert into statement Key: FLINK-15395 URL: https://issues.apache.org/jira/browse/FLINK-15395 Project: Flink Issue Type: Bug

Re: Flink 1.9 SQL Kafka Connector，Json format，how to deal with not json message?

Hi LakeShen, I'm sorry there is no such configuration for json format currently. I think it makes sense to add such configuration like 'format.ignore-parse-errors' in csv format. I created FLINK-15396[1] to track this. Best, Jark [1]: https://issues.apache.org/jira/browse/FLINK-15396 On Thu, 26

[jira] [Created] (FLINK-15397) Streaming and batch has different value in the case of count function

xiaojin.wy created FLINK-15397: -- Summary: Streaming and batch has different value in the case of count function Key: FLINK-15397 URL: https://issues.apache.org/jira/browse/FLINK-15397 Project: Flink

[jira] [Created] (FLINK-15396) Support to ignore parse errors for JSON format

Jark Wu created FLINK-15396: --- Summary: Support to ignore parse errors for JSON format Key: FLINK-15396 URL: https://issues.apache.org/jira/browse/FLINK-15396 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-15398) Correct catalog doc example mistake

Terry Wang created FLINK-15398: -- Summary: Correct catalog doc example mistake Key: FLINK-15398 URL: https://issues.apache.org/jira/browse/FLINK-15398 Project: Flink Issue Type: Bug Com