[jira] [Created] (FLINK-35569) SnapshotFileMergingCompatibilityITCase#testSwitchFromEnablingToDisablingFileMerging failed

Jane Chan created FLINK-35569: - Summary: SnapshotFileMergingCompatibilityITCase#testSwitchFromEnablingToDisablingFileMerging failed Key: FLINK-35569 URL: https://issues.apache.org/jira/browse/FLINK-35569

[jira] [Created] (FLINK-35473) FLIP-457: Improve Table/SQL Configuration for Flink 2.0

Jane Chan created FLINK-35473: - Summary: FLIP-457: Improve Table/SQL Configuration for Flink 2.0 Key: FLINK-35473 URL: https://issues.apache.org/jira/browse/FLINK-35473 Project: Flink Issue Type

[RESULT][VOTE] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

Hi all, I'm happy to announce that FLIP-457[1] has been accepted. There are 11 votes, of which 6 are binding[2]. - Benchao Li (binding) - Leonard Xu (binding) - Lincoln Lee (binding) - Jark Wu (binding) - Rui Fan (binding) - Weijie Guo (binding) - Feng Jin (non-binding) - Hang Ruan (non-binding

[VOTE] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

Hi all, I'd like to start a vote on FLIP-457[1] after reaching a consensus through the discussion thread[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/pages/viewpage.action?pageId=307136992 [2] https:/

Re: [DISCUSSION] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

mat of FLIP so that it can display all content in > one page. > > Best, > Leonard > > > > 2024年5月22日 下午3:42，Jane Chan 写道： > > > > Hi Lincoln, > > > > Thanks for your suggestion. I've reviewed the comments from the previous > PR > >

Re: [DISCUSSION] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

wrote: > Hi Jane, > > Thanks for the updates! > > Just one small comment on the options in IncrementalAggregateRule > & RelNodeBlock, should we also change the API level from Experimental > to PublicEvolving? > > > Best, > Lincoln Lee > > > Jane Chan 于202

Re: [DISCUSSION] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

gt; > > > > Hi Jane, > > > > > > > > > > Thanks for the proposal. +1 from my side. > > > > > > > > > > > > > > > Best, > > > > > Jark > > > > > > > > > > On Thu, 16 Ma

[DISCUSSION] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

Hi all, I'd like to start a discussion on FLIP-457: Improve Table/SQL Configuration for Flink 2.0 [1]. This FLIP revisited all Table/SQL configurations to improve user-friendliness and maintainability as Flink moves toward 2.0. I am looking forward to your feedback. Best regards, Jane [1] https

Re: [VOTE] FLIP-436: Introduce Catalog-related Syntax

Name | > > cat2 | > > | Type | > > generic_in_memory | > > | Comment | > > | > > | Properties | ('default-database','db'), > > ('type','generic_in_memory') | > > > > > +---

Re: [VOTE] FLIP-436: Introduce Catalog-related Syntax

+1 (binding) Best, Jane On Tue, Mar 19, 2024 at 9:30 PM Leonard Xu wrote: > +1(binding) > > > Best, > Leonard > > 2024年3月19日 下午9:03，Lincoln Lee 写道： > > > > +1 (binding) > > > > Best, > > Lincoln Lee > > > > > > Feng Jin 于2024年3月19日周二 19:59写道： > > > >> +1 (non-binding) > >> > >> Best, > >> Fen

Re: [DISCUSS] FLIP-424: Asynchronous State APIs

;Compose' or 'Apply' to interfaces > (onNextCompose, onNextAccept) matching the functions of corresponding APIs > from 'StateFuture'. WDYT? But I'd prefer the former since it is more > simple. > > > Best, > Zakelly > > On Tue, Mar 19, 2024 at 6:09 P

Re: [DISCUSS] FLIP-424: Asynchronous State APIs

Hi Zakelly, Thanks for bringing this discussion. I'm +1 for the overall API design, except for one minor comment about the name of StateIterator#onHasNext since I feel it is a little bit unintuitive. Meanwhile, I asked the opinion from GPT, here's what it said The prefix "on" is commonly used in

[jira] [Created] (FLINK-34669) Optimization of Arch Rules for Connector Constraints and Violation File Updates

Jane Chan created FLINK-34669: - Summary: Optimization of Arch Rules for Connector Constraints and Violation File Updates Key: FLINK-34669 URL: https://issues.apache.org/jira/browse/FLINK-34669 Project

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

ubsequent patch > releases. > > > > Matthias > > > > [1] https://issues.apache.org/jira/browse/FLINK-34227 > > > > On Thu, Mar 14, 2024 at 8:49 AM Jane Chan wrote: > > > > > Hi Yun, Jing, Martijn and Lincoln, > > > > > >

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

file: OK > > > - diffed source distribution with tag, make sure there is no > > > unexpected files: OK > > > - build from source : OK > > > - start a local cluster, played with jdbc connector: OK > > > > > > weijie guo 于2024年3月12日周二 16:55写道： > >

Re: [DISCUSS] FLIP-436: Introduce "SHOW CREATE CATALOG" Syntax

Hi Yubin, Thanks for leading the discussion. I'm +1 for the FLIP. As Jark said, it's a good opportunity to enhance the syntax for Catalog from a more comprehensive perspective. So, I suggest expanding the scope of this FLIP by focusing on the mechanism instead of one use case to enhance the overa

Re: [DISCUSS] FLIP-434: Support optimizations for pre-partitioned data sources

(value = ProjectPushDownSpec.class), > @JsonSubTypes.Type(value = ReadingMetadataSpec.class), > @JsonSubTypes.Type(value = WatermarkPushDownSpec.class), > @JsonSubTypes.Type(value = SourceWatermarkSpec.class), > @JsonSubTypes.Type(value = AggregatePushDownSpec.class), > + @JsonSubTypes.T

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

+1 (non-binding) - Verify that the source distributions do not contain any binaries; - Build the source distribution to ensure all source files have Apache headers; - Verify checksum and GPG signatures; Best, Jane On Tue, Mar 12, 2024 at 4:08 PM Xuannan Su wrote: > +1 (non-binding) > > - Verif

Re: [DISCUSS] FLIP-434: Support optimizations for pre-partitioned data sources

Hi Jeyhun, Thank you for leading the discussion. I'm generally +1 with this proposal, along with some questions. Please see my comments below. 1. Concerning the `sourcePartitions()` method, the partition information returned during the optimization phase may not be the same as the partition infor

Re: [DISCUSS] FLIP-425: Asynchronous Execution Model

Hi Yanfei, Thanks for driving the discussion! I have a few questions from the SQL perspective (and may have some follow-ups). 1. Currently, there are some mini-batch optimizations[1][2] in SQL that update the state during the prepare snapshot phase, which will explicitly call setCurrentKey in the

Re: [ANNOUNCE] New Apache Flink Committer - Jiabao Sun

Congrats, Jiabao! Best, Jane On Tue, Feb 20, 2024 at 10:32 AM Paul Lam wrote: > Congrats, Jiabao! > > Best, > Paul Lam > > > 2024年2月20日 10:29，Zakelly Lan 写道： > > > >> Congrats! Jiabao! > >

Re: [DISCUSS] Alternative way of posting FLIPs

+1 for option 1. Hi Yun, > I am concerned about whether we can view the history of design docs > If someone has editor permissions, they can also view the editing history of Google Docs[1]. If the change history of the design document is equally important, would it be possible to selectively sha

[jira] [Created] (FLINK-34362) Add argument to reuse connector docs cache in setup_docs.sh to improve build times

Jane Chan created FLINK-34362: - Summary: Add argument to reuse connector docs cache in setup_docs.sh to improve build times Key: FLINK-34362 URL: https://issues.apache.org/jira/browse/FLINK-34362 Project

[jira] [Created] (FLINK-34351) Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

Jane Chan created FLINK-34351: - Summary: Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint Key: FLINK-34351 URL: https://issues.apache.org/jira/browse/FLINK-34351

[jira] [Created] (FLINK-34350) Hugo cannot rebuild site for zh doc

Jane Chan created FLINK-34350: - Summary: Hugo cannot rebuild site for zh doc Key: FLINK-34350 URL: https://issues.apache.org/jira/browse/FLINK-34350 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-34258) Incorrect example of accumulator usage within emitUpdateWithRetract for TableAggregateFunction

Jane Chan created FLINK-34258: - Summary: Incorrect example of accumulator usage within emitUpdateWithRetract for TableAggregateFunction Key: FLINK-34258 URL: https://issues.apache.org/jira/browse/FLINK-34258

Re: [DISCUSS] Support detecting table schema from external files.

Hi Yisha, Thanks for driving this discussion. I think it's a valuable feature, and feel free to go ahead. Best, Jane On Tue, Jan 16, 2024 at 6:58 PM Benchao Li wrote: > Thanks Yisha for bringing up this discussion. Schema inferring is a > very interesting and useful feature, especially when it

Re: Re: [VOTE] FLIP-415: Introduce a new join operator to support minibatch

+1 (binding) Best, Jane On Fri, Jan 19, 2024 at 3:54 PM liu ron wrote: > +1(binding) > > Best, > Ron > > Xuyang 于2024年1月19日周五 13:58写道： > > > +1 (non-binding)-- > > > > Best！ > > Xuyang > > > > > > > > > > > > 在 2024-01-19 13:28:52，"Lincoln Lee" 写道： > > >+1 (binding) > > > > > >Best, >

Re: Re: [DISCUSS] FLIP-415: Introduce a new join operator to support minibatch

Therefore, I propose introducing a new option > 'table.exec.mini-batch.compact-changes-enabled' to precisely control > changelog compaction within minibatch. Then we deprecate the option > 'table.exec.deduplicate.mini-batch.compact-changes-enabled' . The > deduplica

Re: Re: [DISCUSS] FLIP-415: Introduce a new join operator to support minibatch

Hi shuai, Thanks for the update! Regarding the newly introduced configuration, I hold the same concern with Benchao and Xuyang. First of all, in most cases, the fact that users choose to enable mini-batch configuration indicates they are aware of the trade-off between throughput and completeness

[jira] [Created] (FLINK-34060) Migrate UserDefinedTableAggFunctions to JavaUserDefinedTableAggFunctions

Jane Chan created FLINK-34060: - Summary: Migrate UserDefinedTableAggFunctions to JavaUserDefinedTableAggFunctions Key: FLINK-34060 URL: https://issues.apache.org/jira/browse/FLINK-34060 Project: Flink

[jira] [Created] (FLINK-34059) Add documentation on how to use state TTL hint

Jane Chan created FLINK-34059: - Summary: Add documentation on how to use state TTL hint Key: FLINK-34059 URL: https://issues.apache.org/jira/browse/FLINK-34059 Project: Flink Issue Type: Sub

Re: [DISCUSS] FLIP-415: Introduce a new join operator to support minibatch

Hi shuai, Thanks for initiating the discussion. The mini-batch join optimization is very helpful, particularly for optimizing outer join conditions in CDC sources and handling cascade joins. And +1 for the proposal. However, I don't see any details on the proposed "MiniBatchStreamingJoinOperator"

[jira] [Created] (FLINK-34053) Support state TTL hint for group aggregate

Jane Chan created FLINK-34053: - Summary: Support state TTL hint for group aggregate Key: FLINK-34053 URL: https://issues.apache.org/jira/browse/FLINK-34053 Project: Flink Issue Type: Sub-task

Re: Re: [VOTE] Accept Flink CDC into Apache Flink

+1 (non-binding) Best, Jane On Tue, Jan 9, 2024 at 8:41 PM Lijie Wang wrote: > +1 (non-binding) > > Best, > Lijie > > Jiabao Sun 于2024年1月9日周二 19:28写道： > > > +1 (non-binding) > > > > Best, > > Jiabao > > > > > > On 2024/01/09 09:58:04 xiangyu feng wrote: > > > +1 (non-binding) > > > > > > Regar

Re: FW: [ANNOUNCE] New Apache Flink Committer - Alexander Fedulov

Congratulations, Alex! Best, Jane On Thu, Jan 4, 2024 at 10:03 AM Junrui Lee wrote: > Congratulations, Alex! > > Best, > Junrui > > weijie guo 于2024年1月4日周四 09:57写道： > > > Congratulations, Alex! > > > > Best regards, > > > > Weijie > > > > > > Steven Wu 于2024年1月4日周四 02:07写道： > > > > > Congra,

Re: [DISCUSS][FLINK-31830] Align the Nullability Handling of ROW between SQL and TableAPI

out we work together on this topic and create a FLIP for this? We > need more examples in a unified document. Currently, the proposal is > split across multiple Flink and Calcite JIRA issues and a ML discussion. > > Regards, > Timo > > > [1] https://issues.apache.org/jira/brow

Re: Re: [DISCUSS][FLINK-31830] Align the Nullability Handling of ROW between SQL and TableAPI

ane and Sergey's proposal! > > > >+1 to correct the Table API behavior. > > > >I have one question: Is the influence only limited to the RowType? Does > the > >Map or Array type have the same problems? > > > >Best, > >Shengkai > >[DISCUSS

[DISCUSS][FLINK-31830] Align the Nullability Handling of ROW between SQL and TableAPI

Dear devs, Several issues [1][2][3] have been identified regarding the inconsistent treatment of ROW type nullability between SQL and TableAPI. However, addressing these discrepancies might necessitate updates to the public API. Therefore, I'm initiating this discussion to engage the community in

Re: Re: Re: [DISCUSS] FLIP-392: Deprecate the Legacy Group Window Aggregation

logic about fallback > to legacy legacy group window agg inside the exec node instead of physical > node. > > > > -- > > Best！ > Xuyang > > > > > > At 2023-12-11 20:38:25, "Jane Chan" wrote: > >Hi Xuyang, > > > >Thanks for drivi

Re: Re: [DISCUSS] FLIP-392: Deprecate the Legacy Group Window Aggregation

Hi Xuyang, Thanks for driving this discussion. I briefly reviewed the first PoC code[1] you provided for implementing the session window TVF, and I noticed a problem. In the `translateToExecNode` method of `StreamPhysicalWindowAggregate`, the session window TVF is translated into the legacy `Stre

[jira] [Created] (FLINK-33719) Cleanup the usage of deprecated StreamTableEnvironment#toRetractStream

Jane Chan created FLINK-33719: - Summary: Cleanup the usage of deprecated StreamTableEnvironment#toRetractStream Key: FLINK-33719 URL: https://issues.apache.org/jira/browse/FLINK-33719 Project: Flink

[jira] [Created] (FLINK-33718) Cleanup the usage of deprecated StreamTableEnvironment#toAppendStream

Jane Chan created FLINK-33718: - Summary: Cleanup the usage of deprecated StreamTableEnvironment#toAppendStream Key: FLINK-33718 URL: https://issues.apache.org/jira/browse/FLINK-33718 Project: Flink

[jira] [Created] (FLINK-33717) Cleanup the usage of deprecated StreamTableEnvironment#fromDataStream(DataStream, Expression...)

Jane Chan created FLINK-33717: - Summary: Cleanup the usage of deprecated StreamTableEnvironment#fromDataStream(DataStream, Expression...) Key: FLINK-33717 URL: https://issues.apache.org/jira/browse/FLINK-33717

[jira] [Created] (FLINK-33716) Cleanup the usage of deprecated StreamTableEnvironment#createTemporaryView(String, DataStream, Expression...)

Jane Chan created FLINK-33716: - Summary: Cleanup the usage of deprecated StreamTableEnvironment#createTemporaryView(String, DataStream, Expression...) Key: FLINK-33716 URL: https://issues.apache.org/jira/browse/FLINK

Re: [NOTICE] flink-table-planner module has been migrated to JUnit5

Thanks Leonard and Jiabao for your tremendous efforts in this regard! Best, Jane On Wed, Nov 22, 2023 at 2:42 PM Leonard Xu wrote: > Hi, all > > There are a lot of JUnit4 tests in flink-table-planner module, but now > Jiabao and I have just migrated all tests to JUnit5 through FLINK-29451[1]. >

Re: [DISCUSS][FLINK-32993] Datagen connector handles length-constrained fields according to the schema definition by default

tly, the Datagen connector generates data that doesn't match the > schema definition > when dealing with fixed-length and variable-length fields. It defaults to > a unified length of 100 > and requires manual configuration by the user. This violates the > correctness of schema constraints

[jira] [Created] (FLINK-33397) FLIP-373: Support Configuring Different State TTLs using SQL Hint

Jane Chan created FLINK-33397: - Summary: FLIP-373: Support Configuring Different State TTLs using SQL Hint Key: FLINK-33397 URL: https://issues.apache.org/jira/browse/FLINK-33397 Project: Flink

[RESULT][VOTE] FLIP-373: Support Configuring Different State TTLs using SQL Hint

Dear developers, FLIP-373 [1] has been accepted and voted through this thread [2]. The proposal received nine approving votes, five of which are binding, and there is no disapproval. Benchao Li (binding) Lincoln Lee (binding) Liu Ron (binding) Jark Wu (binding) Sergey Nuyanzin (binding) Jiabao S

Re: [DISCUSS] FLIP-377: Support configuration to disable filter push down for Table/SQL Sources

ake > "table.optimizer.source.predicate" invalid. > >> The planner will still push down predicates to all sources. > >> Whether filter pushdown is allowed or not is determined by the specific > source's "scan.filter-push-down.enabled" configuration. > >&

Re: [DISCUSS] FLIP-377: Support configuration to disable filter push down for Table/SQL Sources

> Best, > Jiabao > > > > 2023年10月25日 11:56，Benchao Li 写道： > > > > I agree with Jane that fine-grained configurations should have higher > > priority than job level configurations. > > > > For current proposal, we can achieve that: > > - Set "

Re: [DISCUSS] FLIP-377: Support configuration to disable filter push down for Table/SQL Sources

M Jiabao Sun wrote: > Thanks Jane, > > I believe that the configuration "table.optimizer.source.predicate" has a > higher priority at the planner level than the configuration at the source > level, > and it seems easy to implement now. > > Best, > Jiabao > > > &g

Re: [DISCUSS] FLIP-377: Support configuration to disable filter push down for Table/SQL Sources

Hi Jiabao, Thanks for driving this discussion. I have a small question that will "scan.filter-push-down.enabled" take precedence over "table.optimizer.source.predicate" when the two parameters might conflict each other? Best, Jane On Tue, Oct 24, 2023 at 5:05 PM Jiabao Sun wrote: > Thanks Jark

Re: Re: [DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

Jane for driving this exciting feature, looking forward to the vote! > > Jane Chan 于2023年10月23日周一 09:40写道： > > > > Hi, devs, > > > > Thanks for all the feedback. > > > > Based on the discussion [1], we seem to have a consensus, so I would like > > to sta

[VOTE] FLIP-373: Support Configuring Different State TTLs using SQL Hint

Hi developers, Thanks for all the feedback on FLIP-373: Support Configuring Different State TTLs using SQL Hint [1]. Based on the discussion [2], we have reached a consensus, so I'd like to start a vote. The vote will last for at least 72 hours (Oct. 26th at 10:00 A.M. GMT) unless there is an obj

Re: Re: [DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

s you mentioned, omitting the > key can introduce a lot of ambiguity, especially in nested query > blocks. I agree that we should not support this syntax. > > > Thanks a lot for clarifying this for me. > > > Best, > Zakelly > > > On Fri, Oct 13, 2023 at 4:59 PM Ja

Re: [VOTE] FLIP-366: Support standard YAML for FLINK configuration

+1 (non-binding) Best, Jane On Fri, Oct 13, 2023 at 11:20 AM Yuxin Tan wrote: > +1(non-binding) > > Best, > Yuxin > > > Zhanghao Chen 于2023年10月13日周五 10:54写道： > > > +1 (non-binding) > > > > Best, > > Zhanghao Chen > > > > From: Junrui Lee > > Sent: Friday, Octo

Re: Re: [DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

On Thu, Oct 12, 2023 at 7:02 PM Zakelly Lan wrote: > Thanks Jane for clarifying this. I'm ok with keeping the current hint > pattern with the table name specified by key. Just thinking if there > is another simpler way to define the hint. What if an omitted key hint > only applied

Re: [VOTE] FLIP-367: Support Setting Parallelism for Table/SQL Sources

+1 (non-binding) Best, Jane On Wed, Oct 11, 2023 at 5:13 PM Samrat Deb wrote: > +1 (non binding) > > On Wed, 11 Oct 2023 at 1:29 PM, Martijn Visser > wrote: > > > +1 (binding) > > > > On Wed, Oct 11, 2023 at 9:15 AM Sergey Nuyanzin > > wrote: > > > > > > +1 (binding) > > > > > > that's a nice

Re: Re: [DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

> > > > > > > > > > I think this syntax will be easier for users to set operator ttl. So > > big > > > > +1. I left some minor comments here. > > > > > > > > > > > > I notice that using STATE_TTL hints wrongly will not throw any > > except

Re: [DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

ies/deduplication/ > [3] > > https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/topn/ > > > Best, > Feng > > On Sun, Oct 8, 2023 at 5:53 PM Jane Chan wrote: > > > Hi devs, > > > > I'd like to initiate a discussion on FLI

[DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

Hi devs, I'd like to initiate a discussion on FLIP-373: Support Configuring Different State TTLs using SQL Hint [1]. This proposal is on top of the FLIP-292 [2] to address typical scenarios with unambiguous semantics and hint propagation. I'm looking forward to your opinions! [1] https://cwiki.

Re: [DISCUSS] FLIP-367: Support Setting Parallelism for Table/SQL Sources

primary key in source > schema. If the source will produce update/delete message but a primary key > does not exist, an exception will be thrown. > > Best, > Zhanghao Chen > > 发件人: Jane Chan > 发送时间: 2023年9月20日 15:13 > 收件人: dev@flink.apache.

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

uggestion of using > > > > "flink-conf-default.yaml" > > > > > > to > > > > > > > > represent the default YAML file for Flink 1.x, I have been > > > > considering > > > > > > > > the option of using "

Re: [DISCUSS] FLIP-367: Support Setting Parallelism for Table/SQL Sources

data, if there is a > mismatch > > in parallelism between the source and downstream operators, rebalance is > > used by default. > > > > 2. When the source generates update and delete data, we should require > the > > source to configure a primary key and then

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Hi Junrui, Thanks for driving this FLIP. +1 for adoption of the standard YAML syntax. I just have one minor suggestion. It's a little bit challenging to differentiate between `flink-config.yaml` and `flink-conf.yaml` to determine which one uses the standard syntax at a glance. How about using `fli

Re: [DISCUSS] FLIP-367: Support Setting Parallelism for Table/SQL Sources

simply make exec nodes to take the global default > > > parallelism, but both ways prevent potential chaining opportunity and > I'm > > > not sure if that's good to go. We'll need to give deeper thoughts in it > > and > > > polish our proposal. We're

Re: [DISCUSS] FLIP-367: Support Setting Parallelism for Table/SQL Sources

Hi, Zhanghao, Dewei, Thanks for initiating this discussion. This feature is valuable in providing more flexibility for performance tuning for SQL pipelines. Here are my two cents, 1. In the FLIP, you mentioned concerns about the parallelism of the calc node and concluded to "leave the behavior u

Re: Proposal for Implementing Keyed Watermarks in Apache Flink

Hi Tawfik, In response to this issue, we have authored a research paper outlining a > novel strategy named "keyed watermarks" to address data loss and > substantially enhance data processing accuracy, achieving at least 99% > accuracy in most scenarios. > Sounds like a significant improvement! Lo

[DISCUSS][FLINK-31788][FLINK-33015] Add back Support emitUpdateWithRetract for TableAggregateFunction

Hi devs, Recently, we noticed an issue regarding a feature regression related to Table API. `org.apache.flink.table.functions.TableAggregateFunction` provides an API `emitUpdateWithRetract` [1] to cope with updated values, but it's not being called in the code generator. As a result, even if users

Re: 来自Jiangchuan.Lee的邮件

Hi Jiangchuan, If you already have a JIRA account, you can comment under the issue you're interested in (typically starting with bug fixes or documentation and outlining how you'll do it) and request the committer assign it to you. Best, Jane On Thu, Sep 7, 2023 at 9:45 AM Jiangchuan.Lee wrote:

[jira] [Created] (FLINK-33015) TableAggregateFunction codegen does not eval emitUpdateWithRetract

Jane Chan created FLINK-33015: - Summary: TableAggregateFunction codegen does not eval emitUpdateWithRetract Key: FLINK-33015 URL: https://issues.apache.org/jira/browse/FLINK-33015 Project: Flink

[jira] [Created] (FLINK-32860) Add missing visibility annotation for Table APIs

Jane Chan created FLINK-32860: - Summary: Add missing visibility annotation for Table APIs Key: FLINK-32860 URL: https://issues.apache.org/jira/browse/FLINK-32860 Project: Flink Issue Type

Re: [DISCUSS] Add missing visibility annotation for Table APIs

volution: we will come back to the position where we were but with > extra @Internal maintenance effort. > > Best regards, > Jing > > On Sat, Jul 29, 2023 at 3:01 PM Jane Chan wrote: > > > Hi all, > > > > Thanks for your valuable feedback. Here are my though

Re: [DISCUSS] Add missing visibility annotation for Table APIs

the class annotations: > > > - classes in org.apache.flink.table.catalog.stats.* can be > > @PublicEvolving, > > > because all the classes in there are needed to build the > @PublicEvolving > > > CatalogColumnStatistics. > > > - PeriodicCacheReloadTrigger

[RESULT][VOTE] FLIP-346: Deprecate ManagedTable related APIs

Hi devs, FLIP-346 [1] has been accepted and voted through this thread [2]. There are five approving votes, four of which are binding: - Leonard Xu (binding) - Lincoln Lee (binding) - Liu Ron (non-binding) - Timo Walther (binding) - Yuxia Luo (binding) And there is no disapproval.

[jira] [Created] (FLINK-32656) Deprecate ManagedTable related APIs

Jane Chan created FLINK-32656: - Summary: Deprecate ManagedTable related APIs Key: FLINK-32656 URL: https://issues.apache.org/jira/browse/FLINK-32656 Project: Flink Issue Type: Sub-task

[VOTE] FLIP-346: Deprecate ManagedTable related APIs

Hi developers, Thanks for all the feedback on FLIP-346: Deprecate ManagedTable related APIs[1]. Based on the discussion[2], we have reached a consensus, so I would like to start a vote. The vote will last for at least 72 hours unless there is an objection or insufficient votes. [1] https://cwiki

Re: [DISCUSS] FLIP-346: Deprecate ManagedTable related APIs

Hi, all, Since there are no objections against the FLIP, I'm preparing to start a vote. Please don't hesitate to follow up on this if you have any concerns. Best, Jane On Fri, Jul 21, 2023 at 10:19 AM Jane Chan wrote: > Hi Leonard, > > I got your point and adjusted the

Re: [DISUCSS] Deprecate multiple APIs in 1.18

gt; In addition, if there's no objections from the community on marking > > > `StreamRecordTimestamp` & `ExistingField` as deprecated, you may > consider > > > creating a Jira ticket for it as a sub-task of FLINK-32557. > > > > > > Best, > > > > >

Re: [DISCUSS] FLIP-346: Deprecate ManagedTable related APIs

pache.org/flink/flink-table-store-docs-stable/> > > Best, > Leonard > > > On Jul 20, 2023, at 8:03 PM, Jane Chan wrote: > > > > Hi, all, > > > > Thanks for your opinions. > > > > @Leonard > >> We can remove related document as well,

[DISCUSS] Add missing visibility annotation for Table APIs

Hi, Devs, I would like to start a discussion on adding missing visibility annotation (PublicEvolving / Internal etc.) for Table APIs. The motivation for starting this discussion was during the cleanup of which Table API to be deprecated for version 2.0, I noticed that some of the APIs lack visibi

Re: [DISCUSS] FLIP-346: Deprecate ManagedTable related APIs

er < > martijnvis...@apache.org> > > > wrote: > > > > > > > > +1 > > > > > > > > On Thu, Jul 20, 2023 at 7:53 AM Xintong Song > > > wrote: > > > > > > > >> +1 > > > >> > > > &

[jira] [Created] (FLINK-32634) Deprecate StreamRecordTimestamp and ExistingField

Jane Chan created FLINK-32634: - Summary: Deprecate StreamRecordTimestamp and ExistingField Key: FLINK-32634 URL: https://issues.apache.org/jira/browse/FLINK-32634 Project: Flink Issue Type: Sub

[DISCUSS] FLIP-346: Deprecate ManagedTable related APIs

Hi, devs, I would like to start a discussion on FLIP-346: Deprecate ManagedTable related APIs[1]. These APIs were initially designed for Flink Table Store, which has joined the Apache Incubator as a separate project called Apache Paimon(incubating). Since they are obsolete and not used by Paimon

Re: [DISUCSS] Deprecate multiple APIs in 1.18

emoved. As for the internal and test code dependencies, I don't see any > problem in gradually migrating them. > > Best, > > Xintong > > > [1] https://lists.apache.org/thread/734zhkvs59w2o4d1rsnozr1bfqlr6rgm > > [2] https://issues.

Re: [DISUCSS] Deprecate multiple APIs in 1.18

Hi Xintong, Thanks for driving this topic. Regarding the Table API deprecation, I can provide some details to help with the process. 1. This sheet summarizes the user-facing classes an

Re: [ANNOUNCE] Apache Flink has won the 2023 SIGMOD Systems Award

Congratulations! Best, Jane On Thu, Jul 6, 2023 at 2:15 PM Jiadong Lu wrote: > Congratulations! > > Best regards, > Jiadong Lu > > On 2023/7/6 13:26, Weihua Hu wrote: > > Congratulations! > > > > Best, > > Weihua > > > > > > On Wed, Jul 5, 2023 at 5:46 PM Shammon FY wrote: > > > >> Congratulat

[jira] [Created] (FLINK-32374) ExecNodeGraphInternalPlan#writeToFile should support TRUNCATE_EXISTING for overwriting

Jane Chan created FLINK-32374: - Summary: ExecNodeGraphInternalPlan#writeToFile should support TRUNCATE_EXISTING for overwriting Key: FLINK-32374 URL: https://issues.apache.org/jira/browse/FLINK-32374

Re: Re: [VOTE] FLIP-311: Support Call Stored Procedure

+1 (non-binding) Best, Jane On Wed, Jun 14, 2023 at 10:41 AM Feng Jin wrote: > +1 (no-binding) > > > Best, > Feng > > > On Wed, Jun 14, 2023 at 7:02 AM Jing Ge > wrote: > > > +1(binding) > > > > Best Regards, > > Jing > > > > On Tue, Jun 13, 2023 at 9:03 AM Mang Zhang wrote: > > > > > +1 (no-

Re: [DISCUSS] FLIP-311: Support Call Stored Procedure

Hi Yuxia, Thanks for bringing this to the discussion. The call procedure is a widely used feature and will be very useful for users. I just have one question regarding the usage. The FLIP mentioned that Flink will allow connector developers to develop their own built-in stored > procedures, and

[jira] [Created] (FLINK-32245) NonDeterministicTests #testTemporalFunctionsInBatchMode failure masked due to incorrect test initialization

Jane Chan created FLINK-32245: - Summary: NonDeterministicTests #testTemporalFunctionsInBatchMode failure masked due to incorrect test initialization Key: FLINK-32245 URL: https://issues.apache.org/jira/browse/FLINK

[jira] [Created] (FLINK-32064) Add sub-directory of test output file for JsonPlanTest to indicate the plan's version

Jane Chan created FLINK-32064: - Summary: Add sub-directory of test output file for JsonPlanTest to indicate the plan's version Key: FLINK-32064 URL: https://issues.apache.org/jira/browse/FLINK-

[jira] [Created] (FLINK-32053) Introduce StateMetadata to ExecNode to support configure operator-level state TTL via CompiledPlan

Jane Chan created FLINK-32053: - Summary: Introduce StateMetadata to ExecNode to support configure operator-level state TTL via CompiledPlan Key: FLINK-32053 URL: https://issues.apache.org/jira/browse/FLINK-32053

[jira] [Created] (FLINK-32052) Introduce left and right state retention time to StreamingJoinOperator

Jane Chan created FLINK-32052: - Summary: Introduce left and right state retention time to StreamingJoinOperator Key: FLINK-32052 URL: https://issues.apache.org/jira/browse/FLINK-32052 Project: Flink

[jira] [Created] (FLINK-31957) Add documentation for the user story

Jane Chan created FLINK-31957: - Summary: Add documentation for the user story Key: FLINK-31957 URL: https://issues.apache.org/jira/browse/FLINK-31957 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-31956) Extend the CompiledPlan to read from/write to Flink's FileSystem

Jane Chan created FLINK-31956: - Summary: Extend the CompiledPlan to read from/write to Flink's FileSystem Key: FLINK-31956 URL: https://issues.apache.org/jira/browse/FLINK-31956 Project:

[jira] [Created] (FLINK-31952) Support 'EXPLAIN' statement for CompiledPlan

Jane Chan created FLINK-31952: - Summary: Support 'EXPLAIN' statement for CompiledPlan Key: FLINK-31952 URL: https://issues.apache.org/jira/browse/FLINK-31952 Project: Flink Issue Type

[jira] [Created] (FLINK-31950) Introduce StateMetadata and support operator-level state TTL configuration via Compiled Plan

Jane Chan created FLINK-31950: - Summary: Introduce StateMetadata and support operator-level state TTL configuration via Compiled Plan Key: FLINK-31950 URL: https://issues.apache.org/jira/browse/FLINK-31950

[jira] [Created] (FLINK-31917) Loss of Idempotence in JsonSerDe Round Trip for AggregateCall and RexNode

Jane Chan created FLINK-31917: - Summary: Loss of Idempotence in JsonSerDe Round Trip for AggregateCall and RexNode Key: FLINK-31917 URL: https://issues.apache.org/jira/browse/FLINK-31917 Project: Flink

  1   2   3   >