[jira] [Created] (FLINK-29728) TablePlanner prevents Flink from starting is working directory is a symbolic link

Angelo Kastroulis created FLINK-29728: - Summary: TablePlanner prevents Flink from starting is working directory is a symbolic link Key: FLINK-29728 URL: https://issues.apache.org/jira/browse/FLINK-29728

Re: [DISCUSS] REST API to suspend & resume checkpointing

Hi Piotr, Sorry for the confusion. I'm referring to latency concerns at 2 points - 1. In producing a full snapshot, I see this is noted as follows in the Flip [1]: > This means that if the underlying FileSystem doesn’t support fast duplication, incremental savepoints will most likely be still

Re: [DISCUSS] Create a dedicated aws-base connector repository

Thanks Chesnay for the suggestion, I will investigate this option. Related to the single repo idea, I have considered it in the past. Are you proposing we also use a single version between all connectors? If we have a single version then it makes sense to combine them in a single repo, if they

Re: [Cassandra] source connector

There's definitely consensus on externalizing the flink connectors! I've been tracking the progress and I'd be happy to provide support on Cassandra if you'd like. There's some new information at https://cwiki.apache.org/confluence/display/FLINK/Externalized+Connector+development The first step

Re: [DISCUSS] Create a dedicated aws-base connector repository

I agree with Jark. It would be easier for the further development and maintenance, if all aws related connectors and the base module are in the same repo. It might make sense to upgrade the flink-connector-dynamodb to flink-connector-aws and move the other modules including the

[jira] [Created] (FLINK-29727) Fall back to flink-conf.yaml if no JOB_MANAGER_RPC_ADDRESS is specified

Alexander Fedulov created FLINK-29727: - Summary: Fall back to flink-conf.yaml if no JOB_MANAGER_RPC_ADDRESS is specified Key: FLINK-29727 URL: https://issues.apache.org/jira/browse/FLINK-29727

Re: [DISCUSS] Planning Flink 1.17

+1 to feature freeze the 1.17 release on 1.17 (smile), and thanks all for volunteering as our release managers. Looking forward to the soon-released 1.16.0 and the detailed feature plan for 1.17. Best Regards, Yu On Fri, 21 Oct 2022 at 20:17, Jing Ge wrote: > +1 > The plan looks rational.

Re: [DISCUSS] Planning Flink 1.17

+1 The plan looks rational. Thanks for your effort! Best regards, Jing On Fri, Oct 21, 2022 at 1:16 PM Congxian Qiu wrote: > Thanks for kicking off the 1.17 release, and volunteers as release > managers. > > +1 to the feature freeze date > > Best, > Congxian > > > Yun Tang 于2022年10月21日周五

[jira] [Created] (FLINK-29726) Supports hive stddev_samp function by native implementation

dalongliu created FLINK-29726: - Summary: Supports hive stddev_samp function by native implementation Key: FLINK-29726 URL: https://issues.apache.org/jira/browse/FLINK-29726 Project: Flink Issue

[jira] [Created] (FLINK-29725) Supports hive std function by native implementation

dalongliu created FLINK-29725: - Summary: Supports hive std function by native implementation Key: FLINK-29725 URL: https://issues.apache.org/jira/browse/FLINK-29725 Project: Flink Issue Type:

[jira] [Created] (FLINK-29724) Supports hive last_value function by native implementation

dalongliu created FLINK-29724: - Summary: Supports hive last_value function by native implementation Key: FLINK-29724 URL: https://issues.apache.org/jira/browse/FLINK-29724 Project: Flink Issue

[jira] [Created] (FLINK-29723) Supports hive first_value function by native implementation

dalongliu created FLINK-29723: - Summary: Supports hive first_value function by native implementation Key: FLINK-29723 URL: https://issues.apache.org/jira/browse/FLINK-29723 Project: Flink Issue

[jira] [Created] (FLINK-29722) Supports hive max function by native implementation

dalongliu created FLINK-29722: - Summary: Supports hive max function by native implementation Key: FLINK-29722 URL: https://issues.apache.org/jira/browse/FLINK-29722 Project: Flink Issue Type:

[jira] [Created] (FLINK-29721) Supports hive min function by native implementation

dalongliu created FLINK-29721: - Summary: Supports hive min function by native implementation Key: FLINK-29721 URL: https://issues.apache.org/jira/browse/FLINK-29721 Project: Flink Issue Type:

[jira] [Created] (FLINK-29720) Supports hive average function by native implemetatoin

dalongliu created FLINK-29720: - Summary: Supports hive average function by native implemetatoin Key: FLINK-29720 URL: https://issues.apache.org/jira/browse/FLINK-29720 Project: Flink Issue Type:

[jira] [Created] (FLINK-29718) Supports hive sum function by native implementation

dalongliu created FLINK-29718: - Summary: Supports hive sum function by native implementation Key: FLINK-29718 URL: https://issues.apache.org/jira/browse/FLINK-29718 Project: Flink Issue Type:

[jira] [Created] (FLINK-29719) Supports hive count function by native implementation

dalongliu created FLINK-29719: - Summary: Supports hive count function by native implementation Key: FLINK-29719 URL: https://issues.apache.org/jira/browse/FLINK-29719 Project: Flink Issue Type:

Re: [DISCUSS] Create a dedicated aws-base connector repository

How about creating a new repository flink-connector-aws and merging dynamodb, kinesis firehouse into it? This can reduce the maintenance for complex dependencies and make the release easy. I think the maintainers of aws-releated connectors are the same people. Best, Jark > 2022年10月21日

Re: [DISCUSS] Planning Flink 1.17

Thanks for kicking off the 1.17 release, and volunteers as release managers. +1 to the feature freeze date Best, Congxian Yun Tang 于2022年10月21日周五 17:24写道： > Thanks, Qingsheng and Leonard to kick off the release plan of flink-1.17, > which targets a feature freeze date of January 17th . > >

Re: [VOTE] Release 1.16.0, release candidate #2

+1 (binding) for this release candidate - verified checksum & signature - build from source - tried example jobs with standalone cluster, web ui & logs look good - the new completed jobs & history server features work as expected - the new hybrid shuffle mode works as expected Best, Xintong

[jira] [Created] (FLINK-29717) Supports hive udaf such as sum/count by native implementation

dalongliu created FLINK-29717: - Summary: Supports hive udaf such as sum/count by native implementation Key: FLINK-29717 URL: https://issues.apache.org/jira/browse/FLINK-29717 Project: Flink

Re: [Cassandra] source connector

Hi, Yes sure, if there is a consensus on moving, just tell me where to move my PR to. Best Etienne Le 19/10/2022 à 18:20, Alexander Fedulov a écrit : Hi Etienne, thanks for your contribution. In light of the current efforts to externalize connectors, do you think we could maybe combine

Re: [DISCUSS] Create a dedicated aws-base connector repository

I would not go with 2); I think it'd just be messy . Here's another option: Create another repository (aws-connector-base) (following the externalization model), add it as a sub-module to the downstream repositories, and make it part of the release process of said connector. I.e., we never

Re: [DISCUSS] Planning Flink 1.17

Thanks, Qingsheng and Leonard to kick off the release plan of flink-1.17, which targets a feature freeze date of January 17th . +1 to include Martijn and Matthias as the release managers. Best, Yun Tang From: Piotr Nowojski Sent: Friday, October 21, 2022 16:22

Re: [VOTE] Externalized connector release details​

Of course we can (and will). That will happen at a later time once we get a bit of use out of it to iterate faster. On 20/10/2022 18:23, Steven Wu wrote: Chesnay, thanks for the write-up. very helpful! Regarding the parent pom, I am wondering if it can be published to the

[jira] [Created] (FLINK-29716) Separate slf4j jar in the lib folder from the distribution

Alexis Sarda-Espinosa created FLINK-29716: - Summary: Separate slf4j jar in the lib folder from the distribution Key: FLINK-29716 URL: https://issues.apache.org/jira/browse/FLINK-29716 Project:

Re: [DISCUSS] REST API to suspend & resume checkpointing

Hi Saurabh, > 1. Stop with native savepoint does solve any races and produces a > predictable restoration point, but producing a self-contained snapshot and > using CLAIM mode in re-running is not necessary here and adds latency. Why do you think it adds latency? CLAIM mode is actually the

[jira] [Created] (FLINK-29715) Expose max_parallelism in JSON plan

Gyula Fora created FLINK-29715: -- Summary: Expose max_parallelism in JSON plan Key: FLINK-29715 URL: https://issues.apache.org/jira/browse/FLINK-29715 Project: Flink Issue Type: Improvement

Re: [DISCUSS] Planning Flink 1.17

Hi, Thanks for kicking this discussion off Qingsheng and Leonard. I like the January 17th, 2023 touch :) 1 for including Matthias Pohl and Martijn Visser as release managers. Best, Piotrek Always alright pt., 21 paź 2022 o 05:55 Yuan Mei napisał(a): > Thanks, Qingsheng for the kicking-off

Re: SQL Gateway and SQL Client

Sorry for the late response. In the next version(Flink 1.17), we plan to support the SQL Client to submit the statement to the Flink SQL Gateway. The FLINK-29486 is the first step to remove the usage of the `Parser` in the client side, which

[jira] [Created] (FLINK-29714) Merge TableWrite and TableCompact into one interface

Caizhi Weng created FLINK-29714: --- Summary: Merge TableWrite and TableCompact into one interface Key: FLINK-29714 URL: https://issues.apache.org/jira/browse/FLINK-29714 Project: Flink Issue

Re: Modify savepoints in Flink

Sorry. Ignore. Moved this question to the user. On Fri, Oct 21, 2022 at 1:22 PM Sriram Ganesh wrote: > Hi All, > > I am working on a scenario where I need to modify the existing savepoint > operator state. Ex: Wanted to remove some offset of the savepoint. > > What is the better practice for

[jira] [Created] (FLINK-29713) Kubernetes operator should restart failed jobs

Peter Vary created FLINK-29713: -- Summary: Kubernetes operator should restart failed jobs Key: FLINK-29713 URL: https://issues.apache.org/jira/browse/FLINK-29713 Project: Flink Issue Type:

Modify savepoints in Flink

Hi All, I am working on a scenario where I need to modify the existing savepoint operator state. Ex: Wanted to remove some offset of the savepoint. What is the better practice for these scenarios?. Could you please help me with any example as such? Thanks in advance. -- *Sriram G* *Tech*

Re: [DISCUSS] Drop TypeSerializerConfigSnapshot and savepoint support from Flink versions < 1.8.0

Makes sense to me. The serializer stack is pretty complex right now, the more legacy we remove the better. Regards, Timo On 20.10.22 12:49, Chesnay Schepler wrote: +1 Sounds like a good reason to drop these long-deprecated APIs. On 19/10/2022 15:13, Piotr Nowojski wrote: Hi devs, I would