Re: [VOTE] FLIP-489: Add missing dropTable/dropView methods to TableEnvironment
+1(binding) Best, Ron Leonard Xu 于2024年12月15日周日 16:12写道： > Thanks Sergey for driving this FLIP, > > +1(binding) > > Best, > Leonard > > > > > > On Dec 13, 2024, at 6:48 PM, Timo Walther wrote: > > > > +1 (binding) > > > > Thanks, > > Timo > > > > > > On 13.12.24 01:37, Jim Hughes wrote: > >> Hi Sergey, > >> +1 (non-binding) > >> Cheers, > >> Jim > >> On Thu, Dec 12, 2024 at 2:51 PM Sergey Nuyanzin > wrote: > >>> Hi everyone, > >>> > >>> I'd like to start a vote on FLIP-489: Add missing dropTable/dropView > >>> methods > >>> to TableEnvironment [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. > >>> > >>> [1] > >>> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=332499781 > >>> [2] https://lists.apache.org/thread/3b6ohofz4hqvzxmxjwnls9m09s1ch7sk > >>> -- > >>> Best regards, > >>> Sergey > >>> > > > >
Re: [VOTE] FLIP-489: Add missing dropTable/dropView methods to TableEnvironment
Thanks Sergey for driving this FLIP, +1(binding) Best, Leonard > On Dec 13, 2024, at 6:48 PM, Timo Walther wrote: > > +1 (binding) > > Thanks, > Timo > > > On 13.12.24 01:37, Jim Hughes wrote: >> Hi Sergey, >> +1 (non-binding) >> Cheers, >> Jim >> On Thu, Dec 12, 2024 at 2:51 PM Sergey Nuyanzin wrote: >>> Hi everyone, >>> >>> I'd like to start a vote on FLIP-489: Add missing dropTable/dropView >>> methods >>> to TableEnvironment [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. >>> >>> [1] >>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=332499781 >>> [2] https://lists.apache.org/thread/3b6ohofz4hqvzxmxjwnls9m09s1ch7sk >>> -- >>> Best regards, >>> Sergey >>> >
Re: [DISCUSS] FLIP-488: Expose Async State Processing and New State APIs in Datastream(V1) APIs
Hi everyone, I'd like to start a vote soon if there is no further discussion. Best, Zakelly On Wed, Dec 11, 2024 at 5:26 PM Zakelly Lan wrote: > Hi Yanfei, > > Thanks for your response! > > The `SingleOutputStreamOperator` is the return type of `process()` or > `sum()`, so the example would be invoking `enableAsyncState()` after the > processing methods, which has been included in the examples within this > FLIP. > > > Best, > Zakelly > > On Wed, Dec 11, 2024 at 3:03 PM Yanfei Lei wrote: > >> Hi Zakelly, >> >> Thank for the proposal! This makes it easy for Datastream (V1) users >> to use async state processing. >> >> Currently, only keyed states can use async state processing, could you >> please add some examples about how `SingleOutputStreamOperator` use >> async state processing? >> >> Zakelly Lan 于2024年12月5日周四 19:32写道： >> > >> > Hi Yunfeng, >> > >> > will this FLIP add `enableAsyncState` to `SingleOutputStreamOperator` as >> > > well? >> > >> > >> > Yes. Thanks for the reminder. >> > >> > >> > Best, >> > Zakelly >> > >> > On Thu, Dec 5, 2024 at 7:21 PM Yunfeng Zhou < >> flink.zhouyunf...@gmail.com> >> > wrote: >> > >> > > Hi Zakelly, >> > > >> > > Thank for the proposal! >> > > >> > > I noticed that it says users can invoke `enableAsyncState` after sum >> or >> > > process, thus will this FLIP add `enableAsyncState` to >> > > `SingleOutputStreamOperator` as well? >> > > >> > > Best, >> > > Yunfeng >> > > >> > > >> > > > 2024年12月4日 20:32，Zakelly Lan 写道： >> > > > >> > > > Hi everyone, >> > > > >> > > > I'd like to start a discussion on FLIP-488: Expose Async State >> Processing >> > > > and New State APIs in Datastream(V1) APIs[1]. >> > > > >> > > > This FLIP allows Datastream users to leverage the capability of >> async >> > > state >> > > > query and disaggregated state management introduced in FLIP-423[2] >> and >> > > its >> > > > sub-FLIPs. >> > > > >> > > > Looking forward to hearing from you! >> > > > >> > > > [1] https://cwiki.apache.org/confluence/x/yIrREw >> > > > [2] https://cwiki.apache.org/confluence/x/R4p3EQ >> > > > >> > > > >> > > > Best, >> > > > Zakelly >> > > >> > > >> >> >> >> -- >> Best, >> Yanfei >> >
[DISCUSS] FLIP-492: Support Query Modifications for Materialized Tables.
Hi, everyone,
I’d like to initiate a discussion on FLIP-492: Support Query Modifications
for Materialized Tables[1].
In FLIP-435[2], we introduced *MATERIALIZED TABLES*. By defining query
logic and specifying data freshness requirements, users can efficiently
build data pipelines, greatly improving development productivity.
FLIP-492 builds on this by addressing a common need: the ability to modify
the query logic of an existing MATERIALIZED TABLE. Two approaches are
proposed:
*1. Modifying the Query Logic: ALTER MATERIALIZED TABLE AS *
Retain historical data while modifying the query logic:
```
ALTER MATERIALIZED TABLE [catalog_name.][db_name.]table_name AS
```
*2. Replacing the Table: CREATE OR REPLACE MATERIALIZED TABLE*
Reconstruct the table with a new query, discarding all historical data:
```
CREATE [OR REPLACE] MATERIALIZED TABLE [catalog_name.][db_name.]table_name
[ ([]) ]
[COMMENT table_comment]
[PARTITIONED BY (partition_column_name1, partition_column_name2, ...)]
[WITH (key1=val1, key2=val2, ...)]
FRESHNESS = INTERVAL '' { SECOND | MINUTE | HOUR | DAY }
[REFRESH_MODE = { CONTINUOUS | FULL }]
AS
```
For a more detailed explanation of this proposal, please refer to the
FLIP-492[1] documentation.
Your feedback and suggestions are highly appreciated to help refine this
proposal further.
Lastly, I’d like to thank Ron and Lincoln (cc’d) for their valuable input
and suggestions during the drafting process.
Looking forward to hearing your thoughts!
Best,
Feng Jin
[1].
https://cwiki.apache.org/confluence/display/FLINK/FLIP-492%3A+Support+Query+Modifications+for+Materialized+Tables
[2].
https://cwiki.apache.org/confluence/display/FLINK/FLIP-435%3A+Introduce+a+New+Materialized+Table+for+Simplifying+Data+Pipelines
[jira] [Created] (FLINK-36905) Update Chinese document to reflect the changes of FLIP-398
Zhanghao Chen created FLINK-36905: - Summary: Update Chinese document to reflect the changes of FLIP-398 Key: FLINK-36905 URL: https://issues.apache.org/jira/browse/FLINK-36905 Project: Flink Issue Type: Sub-task Components: API / Type Serialization System, Documentation Affects Versions: 1.20.0, 2.0.0 Reporter: Zhanghao Chen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-36906) Optimize the logic for determining if a split is finished.
xiaochen.zhou created FLINK-36906: - Summary: Optimize the logic for determining if a split is finished. Key: FLINK-36906 URL: https://issues.apache.org/jira/browse/FLINK-36906 Project: Flink Issue Type: Improvement Reporter: xiaochen.zhou -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [Discuss] Hive connector bump to Flink 1.20
Hi, Peter. Thanks for you suggestion. However, different with Kafka, we already have release versions that support Flink 1.18/1.19/1.20 for Hive[1], although these releases are based on code from the Flink main repository. To avoid confusion for users when making choices and reduce the publishing cycle, so I think that releasing a new version is unnecessary, Considering that no official version in flink-connector-hive repo has been released before, and there is only one merged pr for FLINK-35221 in flink-connector-hive repo[2]. we can release a new version starting from 1.20 or 2.0. Best Regards Yanquan [1]https://mvnrepository.com/artifact/org.apache.flink/flink-connector-hive [2]https://github.com/apache/flink-connector-hive/commits/main/ > 2024年12月13日 22:38，Peter Huang 写道： > > Thanks for the effort +1. Should we release a new version and retire the > support of Flink 1.18 in hive connector? > We have finished this for the Kafka connector > https://issues.apache.org/jira/browse/FLINK-35109 even before the bump > version to Flink 1.20. > > > On Thu, Dec 12, 2024 at 9:48 PM Leonard Xu wrote: > >> +1 from my side, thanks Yanquan for the effort. >> >> Best, >> Leonard >> >>> On Dec 13, 2024, at 12:20 PM, Yanquan Lv wrote: >>> >>> Hi, developers. >>> >>> I would like to start a discuss about Hive connector bump to Flink 1.20. >>> >>> Hive connector externalization was finished in January of this year >> (thanks to all the developers who have driven this work), and the entire >> module was removed in 2.0. However, It seems that there is not available >> release from this external repository, although we have attempted version >> 3.0.0 before[1], it seems that it has not been completed. The currently >> available releases are all based on the Hive module of the Flink main >> repository[2], and it already contains release packages from 1.18 to 1.20. >>> >>> Considering that we will release based on flink-connector-hive[3] in the >> future, I suggest bumping this repository to 1.20 and cherry picking some >> changes from hive module in Flink repository. Since we have not released >> any historical versions, we do not bear the burden of compatibility with >> previous versions. >>> >>> I would like to get some feedback if anyone has any other opinions on >> this suggestion. >>> >>> Best Regards >>> Yanquan >>> >>> [1] https://lists.apache.org/thread/d43kp2ttskd9p42xhg91b2mx34gnflx9 >>> [2] >> https://mvnrepository.com/artifact/org.apache.flink/flink-connector-hive >>> [3] https://github.com/apache/flink-connector-hive >>> >>> >>> >> >>
