Re: [DISCUSS] FLIP-521: Integrating Variant Type into Flink: Enabling Efficient Semi-Structured Data Processing

Hi Xuannan, Can you link the voting thread and add a JIRA link to the FLIP doc? Thanks, Alexey On Wed, May 7, 2025 at 12:28 AM Xuannan Su wrote: > Hi Timo, > > Thanks for the suggestion! > > I updated the FLIP to use `isPrimitive()` and `VariantTypeException`. > > Regarding `JSON()` and `PARSE_

Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin

Congratulations!!! On Thu, Apr 3, 2025 at 4:47 AM Andriy Redko wrote: > Congrats Sergey!!! > > > > Hi everyone, > > > On behalf of the PMC, I'm very happy to announce Sergey Nuyanzin as a > new Flink Committer. > > > Sergey started contributing small improvements to the project in 2018. > Over t

Re: [VOTE] FLIP-456: CompiledPlan support for Batch Execution Mode

7:00 PM Jim Hughes > > >> wrote: > >> > >> > Hi Alexey, > >> > > >> > +1 (non-binding) > >> > > >> > I'm looking forward to parity between streaming and batch bound for > >> > compiled plans! > >>

[RESULT][VOTE] FLIP-456: CompiledPlan support for Batch Execution Mode

Hello everyone, The vote [1] for FLIP-456 [2] is over. The number of required binding votes (3) was reached (total: 5, binding: 3, non-binding: 2). No objections were raised. Binding: - Martijn Visser - Sergey Nuyanzin - Timo Walther Non-binding: - Jim Hughes - Yuepeng Pan PRs

[VOTE] FLIP-456: CompiledPlan support for Batch Execution Mode

Hello everyone, We had a good discussion of FLIP-456: CompiledPlan support for Batch Execution Mode [1]. Discussion thread is here: [2]. Let's start voting on it. The vote will be open for at least 72 hours unless there is an objection or insufficient votes. The FLIP will be considered accepted i

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

Hey all, starting a vote in 24 hours. Unless there are more points to discuss. Thanks, Alexey On Mon, Jun 17, 2024 at 8:28 AM Alexey Leonov-Vendrovskiy < vendrov...@gmail.com> wrote: > Done. There was some accidental removal during editing. > > Thanks, > Alexey > > O

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

jobs to run forever > (days, months, years) – unlike from . " > > Can you update it? > > Cheers, > > Jim > > On Mon, Jun 17, 2024 at 3:16 AM Alexey Leonov-Vendrovskiy < > vendrov...@gmail.com> wrote: > > > Thanks Timo and Jim! Added a few sentences to

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

>> plan and intermediate state; the tests verify that those can work > >>> together > >>>> and continue processing. > >>>> > >>>> For batch execution, I think we just want that all existing compiled > >>> plans > >>>>

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

ing written. > > > > Cheers, > > > > Jim > > > > On Tue, May 7, 2024 at 5:11 AM Paul Lam wrote: > > > >> Hi Alexey, > >> > >> Thanks a lot for bringing up the discussion. I’m big +1 for the FLIP. > >> > >> I sup

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

hangeability of json plans > between batch mode and streaming mode, right? > In other words, a json plan compiled in a batch program can’t be run in > streaming mode without a migration (which is not yet supported). > > Best, > Paul Lam > > > 2024年5月7日 14:38，Alexey L

[DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

Hi everyone, PTAL at the proposed FLIP-456: CompiledPlan support for Batch Execution Mode. It is pretty self-describing. Any thoughts are welcome! Thanks, Alexey [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-456%3A+CompiledPlan+support+for+Batch+Execution+Mode .

[jira] [Created] (FLINK-35241) Support SQL FLOOR and CEIL functions with SECOND and MINUTE for TIMESTAMP_TLZ

Alexey Leonov-Vendrovskiy created FLINK-35241: - Summary: Support SQL FLOOR and CEIL functions with SECOND and MINUTE for TIMESTAMP_TLZ Key: FLINK-35241 URL: https://issues.apache.org/jira/browse/FLINK

Re: Making CollectSinkFunction to wait till all results are consumed

aths where someone wants to use the > `CollectSinkFunction` but doesn't want the results to be read > automatically? And if there are, can we tell them apart? > > Best, > Piotrek > > pon., 12 lut 2024 o 08:48 Alexey Leonov-Vendrovskiy > napisał(a): > > > Hey

Making CollectSinkFunction to wait till all results are consumed

Hey all, We propose to slightly change the behavior of the CollectSinkFunction and make it wait till all

Re: [VOTE] FLIP-387: Support named parameters for functions and call procedures

Thanks for starting the vote! Do you mind adding a link from the FLIP to this thread? Thanks, Alexey On Thu, Jan 4, 2024 at 6:48 PM Feng Jin wrote: > Hi everyone > > Thanks for all the feedback about the FLIP-387: Support named parameters > for functions and call procedures [1] [2] . > > I'd li

Re: [DISCUSS] FLIP-348: Support System Columns in SQL and Table API

t;> Built-in pseudo-columns mean that connector or catalog providers > need > > > >>> consensus in Flink which pseudo-columns should be built-in. We > should > > > >>> keep the concept generic and let platform providers decide which > > pseudo > > > >>>

Re: [DISCUSS] FLIP-348: Support System Columns in SQL and Table API

table/query, and pseudo-column > > "$proctime" always returns PROCTIME() value for each table/query. In this > > way, catalogs only need > > to provide a default rowtime attribute and users can get it in the same > > way. And we don't need > > to i

Re: [DISCUSS] FLIP-348: Support System Columns in SQL and Table API

> > `SELECT * FROM (SELECT $rowtime, * FROM t);` > Am I right that it will show `$rowtime` in output ? Yes, all explicitly selected columns become a part of the result (and intermediate) schema, and hence propagate. On Thu, Jul 27, 2023 at 2:40 PM Alexey Leonov-Vendrovskiy

Re: [DISCUSS] FLIP-348: Support System Columns in SQL and Table API

Thank you, Timo, for starting this FLIP! I propose the following change: Remove the requirement that DESCRIBE need to show system columns. Some concrete vendor specific catalog implementations might prefer this approach. Usually the same system columns are available on all (or family) of tables

Re: SQL Gateway and SQL Client

il. If the FLIP passes, we can develop it together. > > > Another question about persistent Gateway: did you have any specific > thoughts about it or some draft design? > > We don't have any detailed plan about this. But I know Livy has a similar > feature. > > Be

Re: SQL Gateway and SQL Client

submit the job > on behalf of the client? > - ... > > For detailed implementation, I think Hive and Presto are good examples to > dig in. If you have some thoughts about the authentication module, > please let me know. > > Best, > Shengkai > > Alexey Leonov-Vendrovs

Re: SQL Gateway and SQL Client

Gateway a > multi-tenant > component? > Yes. > > Shengkaiis the maintainer of SQL Client and SQL gateway, maybe he can > provide more information. > > > > Best regards, > Yuxia > > - 原始邮件 - > 发件人: "Alexey Leonov-Vendrovskiy" > 收件人: "d

SQL Gateway and SQL Client

Hi all, I’m Alexey from Confluent. This is my first email in this discussion list. I’m rather new to Flink, and to local customs of communication. I want to dive deeper and hopefully get more involved over time. Currently I have a few questions around SQL Gateway and SQL Client. Specifically I wa