+1 (non-binding)
Thanks,
Hao
On Mon, Jun 2, 2025 at 11:50 AM Jiaming Xu wrote:
> +1 (non-binding)
>
> > On Jun 2, 2025, at 11:03, Mingge Deng
> wrote:
> >
> > +1
> >
> > On Mon, Jun 2, 2025 at 7:53 AM Yuan Mei wrote:
> >
> >> +1 (binding)
> >>
> >> On Mon, Jun 2, 2025 at 5:07 PM Martijn Visse
Hi Dev,
I'm happy to announce that FLIP-526: Model ML_PREDICT, ML_EVALUATE Table
API [1] has been accepted with 4 approving votes (4 binding) [2].
Timo Walther (binding)
Shengkai Fang (binding)
Piotr Nowojski (binding)
Robert Metzger (binding)
Thanks,
Hao
[1]
https://cwiki.apache.org/confluence
> > > +1 (binding)
> > > >
> > > > We should still check whether changes to QueryOperationVisitor are
> > > > necessary but this is internal API and should not the FLIP. The
> public
> > > > API looks correct to me.
> > > &
Hao Li created FLINK-37849:
--
Summary: Model provider factory discover
Key: FLINK-37849
URL: https://issues.apache.org/jira/browse/FLINK-37849
Project: Flink
Issue Type: Sub-task
Hi Xintong, Sean and Chris,
Thanks for driving the initiative. Very exciting to bring AI Agent to Flink
to empower the streaming use cases.
+1 to the FLIP.
Thanks,
Hao
On Wed, May 21, 2025 at 7:35 AM Nishita Pattanayak <
nishita.pattana...@gmail.com> wrote:
> Hi Sean, Chris and Xintong. This s
+1 (non-binding)
Thanks,
Hao
On Tue, May 20, 2025 at 12:39 PM Piotr Nowojski
wrote:
> Hi,
>
> +1 (binding)
>
> Best, Piotrek
>
> wt., 20 maj 2025 o 20:29 Roman Khachatryan napisał(a):
>
> > Hi everyone,
> >
> > I'd like to start a vote on FLIP-530: Dynamic job configuration
> > [1] which has b
Hao Li created FLINK-37819:
--
Summary: Add column expansion test for model TVF
Key: FLINK-37819
URL: https://issues.apache.org/jira/browse/FLINK-37819
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37799:
--
Summary: Flink native model predict runtime implementation
Key: FLINK-37799
URL: https://issues.apache.org/jira/browse/FLINK-37799
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37796:
--
Summary: Codegen for ml_evaluate
Key: FLINK-37796
URL: https://issues.apache.org/jira/browse/FLINK-37796
Project: Flink
Issue Type: Sub-task
Reporter: Hao
s2z55
On Mon, May 12, 2025 at 9:45 AM Hao Li wrote:
> Hi Timo,
>
> Thanks for letting me know. I'll reopen the vote. Should we update the
> FLIP wiki [1] to include the 72 business hours?
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposa
Hao Li created FLINK-37797:
--
Summary: Documentation
Key: FLINK-37797
URL: https://issues.apache.org/jira/browse/FLINK-37797
Project: Flink
Issue Type: Sub-task
Reporter: Hao Li
Hao Li created FLINK-37793:
--
Summary: Codegen for ml_predict
Key: FLINK-37793
URL: https://issues.apache.org/jira/browse/FLINK-37793
Project: Flink
Issue Type: Sub-task
Reporter: Hao Li
Hao Li created FLINK-37795:
--
Summary: Physical rewrite for ml_evaluate
Key: FLINK-37795
URL: https://issues.apache.org/jira/browse/FLINK-37795
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37794:
--
Summary: ml_evaluate sql function skeleton
Key: FLINK-37794
URL: https://issues.apache.org/jira/browse/FLINK-37794
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37792:
--
Summary: Physical rewrite for ml_predict
Key: FLINK-37792
URL: https://issues.apache.org/jira/browse/FLINK-37792
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37791:
--
Summary: Integrate with sql to rel converter
Key: FLINK-37791
URL: https://issues.apache.org/jira/browse/FLINK-37791
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37790:
--
Summary: Add model factory related interfaces/classes
Key: FLINK-37790
URL: https://issues.apache.org/jira/browse/FLINK-37790
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37789:
--
Summary: Integrate with sqlvalidator
Key: FLINK-37789
URL: https://issues.apache.org/jira/browse/FLINK-37789
Project: Flink
Issue Type: Sub-task
Reporter
Hao Li created FLINK-37780:
--
Summary: ml_predict sql function skeleton
Key: FLINK-37780
URL: https://issues.apache.org/jira/browse/FLINK-37780
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37779:
--
Summary: Add getModel to Flink catalog reader etc
Key: FLINK-37779
URL: https://issues.apache.org/jira/browse/FLINK-37779
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-37778:
--
Summary: model keyword syntax change
Key: FLINK-37778
URL: https://issues.apache.org/jira/browse/FLINK-37778
Project: Flink
Issue Type: Sub-task
Reporter
Hao Li created FLINK-3:
--
Summary: FLIP-525: Model ML_PREDICT, ML_EVALUATE Implementation
Design
Key: FLINK-3
URL: https://issues.apache.org/jira/browse/FLINK-3
Project: Flink
Issue
Hi everyone,
I'd like to start a vote on FLIP-526: Model ML_PREDICT, ML_EVALUATE Table
API [1], which has been discussed in this thread [2].
The vote will be open for at least 72 business hours unless there is an
objection
or not enough votes.
Thanks,
Hao
[1]
https://cwiki.apache.org/confluence
1 (binding)
> >
> > Best,
> > Piotrek
> >
> > niedz., 11 maj 2025 o 18:14 Hao Li
> napisał(a):
> >
> > > Hi Dev,
> > >
> > > Thanks all for voting. I'm closing the vote and the result will be
> posted
> > > in
; Hi Hao,
>
> please note that 72 hours in VOTE threads refers to business days so
> excluding weekends. This vote should be open for at least 1 more day.
>
> Regards,
> Timo
>
>
>
> On 11.05.25 18:19, Hao Li wrote:
> > Hi Dev,
> >
> > I'm h
In the end, most stuff should be reusable from the PTF work.
>
> Cheers,
> Timo
>
>
> On 12.05.25 16:46, Timo Walther wrote:
> > +1 to continue to voting.
> >
> > Thanks,
> > Timo
> >
> > On 11.05.25 18:47, Hao Li wrote:
> >> Hi
Hi all,
If there are no more discussions. I will start voting tomorrow.
Thanks,
Hao
On Thu, May 8, 2025 at 10:38 AM Hao Li wrote:
> Hi Ron,
>
> > whether the predict or evaluate introduced in this FLIP can be
> serialized to SQL?
>
> Yes. It can be serialized to SQL. We
Hi Dev,
I'm happy to announce that FLIP-525: Model ML_PREDICT, ML_EVALUATE
Implementation Design [1] has been accepted with 6 approving votes (3
binding) [2]
Yash Anand (non-binding)
Mayank Juneja (non-binding)
Shengkai Fang (binding)
Ron Liu (binding)
Yunfeng Zhou (non-binding)
Martijn Visser (b
> >
> > Best,
> > Yunfeng
> >
> > > 2025年5月9日 00:01，Hao Li 写道：
> > >
> > > Hi everyone,
> > >
> > > I'd like to start a vote on FLIP-525: Model ML_PREDICT, ML_EVALUATE
> > > Implementation Design [1], which has
+1 (non-binding)
Thanks,
Hao
On Fri, May 9, 2025 at 3:41 AM Arvid Heise wrote:
> +1 (binding)
>
> Cheers
>
> On Wed, May 7, 2025 at 6:37 PM Gustavo de Morais
> wrote:
>
> > Hi everyone,
> >
> > I'd like to start voting on FLIP-516: Multi-Way Join Operator [1]. The
> > discussion can be found i
uable addition!
> > >
> > > Best,
> > > Piotrek
> > >
> > > wt., 29 kwi 2025 o 03:57 Shengkai Fang napisał(a):
> > >
> > > > Hi, Hao.
> > > >
> > > > +1 for the proposal.
> > > >
> > > &g
Hi everyone,
I'd like to start a vote on FLIP-525: Model ML_PREDICT, ML_EVALUATE
Implementation Design [1], which has been discussed in this thread [2].
The vote will be open for at least 72 hours unless there is an objection
or not enough votes.
Thanks,
Hao
[1]
https://cwiki.apache.org/conflue
riate
> to replace task with a word more suited to the scenario, but of course I
> don't have a good suggestion at the moment, just a suggestion.
>
> Best,
> Ron
>
> Hao Li 于2025年5月7日周三 11:24写道：
>
> > Hi Yunfeng, Ron,
> >
> > Thanks for the fee
P! It provides a clearer guideline for developers to
> > implement model functions.
> >
> > One minor comment: it might be better to change the configuration api_key
> > to apikey, which corresponds to GlobalConfiguration.SENSITIVE_KEYS.
> > Otherwise users’ secrets mi
+1 (non-binding)
Thanks for driving this!
Hao
On Tue, May 6, 2025 at 8:27 AM Ferenc Csaky
wrote:
> +1 (binding)
>
> Thanks for driving this!
>
> Best,
> Ferenc
>
>
>
>
> On Tuesday, May 6th, 2025 at 14:50, Sergey Nuyanzin
> wrote:
>
> >
> >
> > Thank you for driving this
> > +1 (binding)
> >
; > Piotrek
> >
> > wt., 29 kwi 2025 o 03:52 Shengkai Fang napisał(a):
> >
> > > Hi, Hao.
> > >
> > > Thanks for your proposal about ML related functions. This FLIP will
> help
> > > others to implement their own model provider.
> >
Thanks Mayank for the proposal. I think it's a great addition to Flink to
define secure connectivity in general for table, model and other resources
later on. +1.
Hao
On Fri, May 2, 2025 at 5:32 AM Gustavo de Morais
wrote:
> Hi Mayank,
>
> Thanks for the initiative. Looking at the FLIP, this lo
Hi All,
I would like to start a discussion about FLIP-526 [1]: Model ML_PREDICT,
ML_EVALUATE Table API.
This FLIP is a follow up of FLIP-507 [2] to propose the table api for model
related functions. This FLIP is also closely related to FLIP-525 [3] which
is the proposal for model related function
Hi All,
I would like to start a discussion about FLIP-525 [1]: Model ML_PREDICT,
ML_EVALUATE Implementation Design. This FLIP is co-authored with Shengkai
Fang.
This FLIP is a follow up of FLIP-437 [2] to propose the implementation
design for ML_PREDICT and ML_EVALUATE function which were introdu
s is usually present in the same
> > classpath and this becomes less of an issue in production. Casting
> > structured types to ROW is also supported.
> >
> > The implementation effort of this FLIP is very low. It's mostly intended
> > to fill missing gaps, no major
ols. The SQL engine
> > will not load the class. Classes are a concept of a JVM or Python API
> > endpoint. This also the reason why a SQL ARRAY can be
> > represented as List, long[], Long[]. The latter are only concepts
> > in the target programming language and might look
Hi Timo,
Thanks for the FLIP. +1 with a few questions:
1. Can `StructuredType` be nested? e.g. `STRUCTURED<'com.example.User',
name STRING, age INT NOT NULL, address STRUCTURED<'com.example.address',
street STRING, zip STRING>>`
2. What's the main reason the class won't be enforced in SQL? Since
Hi Timo,
Any question I have is what's the SEARCH_KEY result schema you have in
mind? Can it output multiple rows for every row in the left table or it
needs to pack the result in a single row as an array?
Thanks,
Hao
On Mon, Mar 24, 2025 at 10:20 AM Hao Li wrote:
> Thanks Timo for
Thanks Timo for the FLIP! This is a great improvement to the FLINK sql
syntax around tables. I have two clarification questions:
1. For SEARCH_KEY
```
SELECT *
FROM
t_other,
LATERAL SEARCH_KEY(
input => t,
on_key => DESCRIPTOR(k),
lookup => t_other.name,
options => MAP[
'
+1 (non-binding)
Thanks Yash,
Hao
On Tue, Feb 18, 2025 at 10:46 AM Yash Anand
wrote:
> Hi Everyone,
>
> I'd like to start a vote on FLIP-507: Add Model DDL methods in TABLE API
> [1] which has been discussed in this thread [2].
>
> The vote will be open for at least 72 hours unless there is an
Hi Yash,
+1 for the proposal.
Thanks,
Hao
On Mon, Feb 10, 2025 at 12:31 AM Yanquan Lv wrote:
> Hi, Yash. Thanks for driving it.
> +1 for this.
>
> > 2025年2月7日 05:28，Yash Anand 写道：
> >
> > Hi all! I would like to open up for discussion a new FLIP-507[1].
> > Motivation This proposal aims to ex
Hao Li created FLINK-35020:
--
Summary: Model Catalog implementation in Hive etc
Key: FLINK-35020
URL: https://issues.apache.org/jira/browse/FLINK-35020
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-35019:
--
Summary: Support show create model syntax
Key: FLINK-35019
URL: https://issues.apache.org/jira/browse/FLINK-35019
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-35017:
--
Summary: ML_PREDICT function
Key: FLINK-35017
URL: https://issues.apache.org/jira/browse/FLINK-35017
Project: Flink
Issue Type: Sub-task
Reporter: Hao Li
Hao Li created FLINK-35018:
--
Summary: ML_EVALUATE function
Key: FLINK-35018
URL: https://issues.apache.org/jira/browse/FLINK-35018
Project: Flink
Issue Type: Sub-task
Reporter: Hao Li
Hao Li created FLINK-35016:
--
Summary: Catalog changes for model CRUD
Key: FLINK-35016
URL: https://issues.apache.org/jira/browse/FLINK-35016
Project: Flink
Issue Type: Sub-task
Reporter
Hao Li created FLINK-35014:
--
Summary: SqlNode to operation conversion for models
Key: FLINK-35014
URL: https://issues.apache.org/jira/browse/FLINK-35014
Project: Flink
Issue Type: Sub-task
Hao Li created FLINK-35013:
--
Summary: Support temporary model
Key: FLINK-35013
URL: https://issues.apache.org/jira/browse/FLINK-35013
Project: Flink
Issue Type: Sub-task
Reporter: Hao
Hi Dev,
I'm happy to announce that FLIP-437: Support ML Models in Flink SQL [1] has
been accepted with 7 approving votes (6 binding) [2]
Timo Walther (binding)
Jark Wu (binding)
Yu Chen (non-binding)
Piotr Nowojski (binding)
Leonard Xu (binding)
Martijn Visser (binding)
David Moravek (binding)
T
Hi Dev,
Thanks all for voting. I'm closing the vote and the result will be posted
in a separate email.
Thanks,
Hao
On Wed, Apr 3, 2024 at 10:24 AM Hao Li wrote:
> Thanks David Radley and David Moravek for the comments. I'll reply in the
> discussion thread.
>
> Hao
>
rent catalog interface extend it. As model support
will be built-in in Flink, the current catalog interface will need to
support model CRUD operations. For my own education, can you elaborate more
on how separate interface will allow us to begin with lower stability
guarantees?
Thanks,
Hao
On Thu, M
does the model have an owner? I assume that Flink model resource is the
> > master of the model? I imagine in the future that a model that comes in
> via
> > a new connector could be kept up to date with the external model and
> would
> > not be allowed to be changed by
Hao Li created FLINK-34993:
--
Summary: Support Model CRUD in parser
Key: FLINK-34993
URL: https://issues.apache.org/jira/browse/FLINK-34993
Project: Flink
Issue Type: Sub-task
Reporter
Hao Li created FLINK-34992:
--
Summary: FLIP-437: Support ML Models in Flink SQL
Key: FLINK-34992
URL: https://issues.apache.org/jira/browse/FLINK-34992
Project: Flink
Issue Type: New Feature
Hi devs,
I'd like to start a vote on the FLIP-437: Support ML Models in Flink
SQL [1]. The discussion thread is here [2].
The vote will be open for at least 72 hours unless there is an objection or
insufficient votes.
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-437%3A+Support+ML+M
Thanks Timo. I'll start a vote tomorrow if no further discussion.
Thanks,
Hao
On Thu, Mar 28, 2024 at 9:33 AM Timo Walther wrote:
> Hi everyone,
>
> I updated the FLIP according to this discussion.
>
> @Hao Li: Let me know if I made a mistake somewhere. I added some
&g
> important
> because it relates to what use cases can run with the new Flink version out
> of the box.
>
> Best,
> Jark
>
> On Wed, 27 Mar 2024 at 01:10, Hao Li wrote:
>
> > Hi Timo,
> >
> > Yeah. For `primary key` and `from table(...)` those are expl
e.
>
> Let me know when you updated the FLIP for a final review before voting.
>
> Do others have additional objections?
>
> Regards,
> Timo
>
> [1]
>
> https://livesql.oracle.com/apex/livesql/file/content_HQK7TYEO0NHSJCDY3LN2ERDV6.html
>
>
>
> On 25.03.2
be deduced from the options.
2). Sure. We can add temporary model
3). Make sense. We can use `show create model ` to display all
information and `describe model ` to show input/output schema
Thanks,
Hao
On Mon, Mar 25, 2024 at 3:21 PM Hao Li wrote:
> Hi Ahmed,
>
> Looks like the feature fr
rameters similar to `DESCRIBE
> TABLE` only shows the columns (not the WITH clause).
>
> Regards,
> Timo
>
>
> On 23.03.24 13:17, Ahmed Hamdy wrote:
> > Hi everyone,
> > +1 for this proposal, I believe it is very useful to the minimum, It
> would
> >
.
> >> >> The specific checking logic of cumulate window happens in
> >> >> SqlCumulateTableFunction.OperandMetadataImpl#checkOperandTypes.
> >> >> The return type of SqlCumulateTableFunction is defined in
> >> >> #getRowTypeInference() me
defining
> the function with the model, users can directly invoke the function without
> reference to the model name.
>
> Best,
> Jark
>
> [1]:
>
> https://github.com/apache/flink/blob/d6c7eee8243b4fe3e593698f250643534dc79cb5/flink-table/flink-table-planner/src/main/ja
%3A+Support+SQL+windowing+table-valued+function#FLIP145:SupportSQLwindowingtablevaluedfunction-CumulatingWindows
> [3]:
>
> https://github.com/aws-samples/amazon-redshift-ml-getting-started/blob/main/use-cases/bring-your-own-model-remote-inference/README.md#create-model
>
>
>
>
>
will we support? How to define a user-defined
> model type?
>
> 5. Regarding the remote model, what providers will we support? Can users
> implement
> 3rd-party providers except OpenAI?
>
> Best,
> Jark
>
> [1]:
>
> https://nightlies.apache.org/flink/flink-docs-master
Hi, Dev
Mingge, Chris and I would like to start a discussion about FLIP-437:
Support ML Models in Flink SQL.
This FLIP is proposing to support machine learning models in Flink SQL
syntax so that users can CRUD models with Flink SQL and use models on Flink
to do prediction with Flink data. The FL
70 matches
Mail list logo
