Re: [VOTE] Release 1.15.1, release candidate #1

Hi Dawid and Konstantin. +0 for this RC. Let's move on. Best, Jingsong On Mon, Jul 4, 2022 at 2:17 PM Konstantin Knauf wrote: > > Thanks Jingsong. I agree that this is a serious bug and we need to take > compatibility seriously. We shouldn't wait long until we release Flink > 1.15.2. Still I s

Re: [DISCUSS] FLIP-245: Source Supports Speculative Execution For Batch Job

Thanks for updating the FLIP! I agree that at the moment users do not need watermark alignment(in which case ReportedWatermarkEvent would happen) in batch cases. However, I think the concept of watermark alignment is not conflicted with speculative execution. It can work with speculative execution

Re: [VOTE] Release 1.15.1, release candidate #1

Thanks Jingsong. I agree that this is a serious bug and we need to take compatibility seriously. We shouldn't wait long until we release Flink 1.15.2. Still I stand to my point, that we shouldn't abort the current release. --- +1 (binding) * checked release blog post * verified signatures and ch

Re: [VOTE] Apache Flink ML Release 2.1.0, release candidate #2

Thanks for raising this release candidate. +1 (non-binding) - Verified that the checksums and GPG files match the corresponding release files. - Verified that the source distributions do not contain any binaries. - Built the source distribution and ensured that all source files have Apache header

[jira] [Created] (FLINK-28369) Support PARSE_URL bulit-in function in Table API

LuNing Wang created FLINK-28369: --- Summary: Support PARSE_URL bulit-in function in Table API Key: FLINK-28369 URL: https://issues.apache.org/jira/browse/FLINK-28369 Project: Flink Issue Type: Im

Re: [DISCUSS] Support partition pruning for streaming reading

Hi zoucao, Look forward your FLIP. >For Batch reading, the 'remainingPartitions' will be seen as the partitions >needed to consume, for streaming reading, we use the >'partitionPruningFunction' to ignore the unneeded partitions. There should be for bounded source(maybe batch or streaming), `apply

Re: Python Job Support for the Kubernetes Operator

AFAIK, the python job could be considered as a special case of jar job. The user jar is flink-python-*.jar and is located in the opt directory. The python script is just the argument of this user jar. So I believe the users already could submit python jobs via Flink Kubernetes operator. However, th

Re: [DISCUSS] Support partition pruning for streaming reading

Hi Martijn, thanks for your attention, I'm glad to create a FLIP, and could you help give me the permission? My Id is zoucao, and my mail is zoucao...@gmail.com. The implications for FileSource In the above discussion, only HiveSource has been involved, because it holds a continuous partition fet

[jira] [Created] (FLINK-28368) Get field type return result problem

hunter created FLINK-28368: -- Summary: Get field type return result problem Key: FLINK-28368 URL: https://issues.apache.org/jira/browse/FLINK-28368 Project: Flink Issue Type: Improvement Co

Re: [VOTE] Release 1.15.1, release candidate #1

Hi Konstantin, I have no problem with canceling -1. However, 1.15.1 will also be a version that is not compatible with 1.14. I've heard too many complaints about connector compatibility, and Flink always introduces incompatible changes to the connector in every release. Flink's new version can le

Re: [DISCUSS] FLIP-238: Introduce FLIP-27-based Data Generator Source

Hi Alex, Yes, that is what I had in mind. We need to add the method getRuntimeContext() to the SourceReaderContext interface as well. Thanks, Jiangjie (Becket) Qin On Mon, Jul 4, 2022 at 3:01 AM Alexander Fedulov wrote: > Hi Becket, > > thanks for your input. I like the idea of adding the par

Re: [DISCUSS] FLIP-238: Introduce FLIP-27-based Data Generator Source

Hi Becket, thanks for your input. I like the idea of adding the parallelism to the SourceReaderContext. My understanding is that any change of parallelism causes recreation of all readers, so it should be safe to consider it "fixed" after the readers' initialization. In that case, it should be as

Python Job Support for the Kubernetes Operator

Hi Devs! Would anyone with a good understanding of the Python execution layer be interested in working on adding Python job support for the Flink Kubernetes Operator? This is a feature request that comes up often ( https://issues.apache.org/jira/browse/FLINK-28364) and it would be a great way to

[jira] [Created] (FLINK-28367) OffsetDateTime does not work with keyBy

Henrik Laxhuber created FLINK-28367: --- Summary: OffsetDateTime does not work with keyBy Key: FLINK-28367 URL: https://issues.apache.org/jira/browse/FLINK-28367 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-28366) Support for custom query for JDBC Table API source connector

Jeya Prakash Thanigaivel created FLINK-28366: Summary: Support for custom query for JDBC Table API source connector Key: FLINK-28366 URL: https://issues.apache.org/jira/browse/FLINK-28366

[jira] [Created] (FLINK-28365) TO_TIMESTAMP lose precision beyond seconds

Lim Qing Wei created FLINK-28365: Summary: TO_TIMESTAMP lose precision beyond seconds Key: FLINK-28365 URL: https://issues.apache.org/jira/browse/FLINK-28365 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-28364) Job types support Python

wu3396 created FLINK-28364: -- Summary: Job types support Python Key: FLINK-28364 URL: https://issues.apache.org/jira/browse/FLINK-28364 Project: Flink Issue Type: New Feature Components: Ku