[jira] [Created] (FLINK-32565) Support cast BYTES to DOUBLE

Hanyu Zheng created FLINK-32565: --- Summary: Support cast BYTES to DOUBLE Key: FLINK-32565 URL: https://issues.apache.org/jira/browse/FLINK-32565 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-32564) Support cast BYTES to BIGINT

Hanyu Zheng created FLINK-32564: --- Summary: Support cast BYTES to BIGINT Key: FLINK-32564 URL: https://issues.apache.org/jira/browse/FLINK-32564 Project: Flink Issue Type: Sub-task

Re: [DISUCSS] Deprecate multiple APIs in 1.18

Hi Alex, I would follow FLIP-197 and try to release them asap depending on dev resources and how difficult those issues are. The fastest timeline is the period defined in FLIP-197 in ideal conditions. Best regards, Jing On Fri, Jul 7, 2023 at 12:20 PM Alexander Fedulov <

Re: [DISUCSS] Deprecate multiple APIs in 1.18

@Xintong > - IIUC, the testing scenario you described is like blocking the source for > proceeding (emit data, finish, etc.) until a checkpoint is finished. It is more tricky than that - we need to prevent the Sink from receiving a checkpoint barrier until the Source is done emitting a given set

[VOTE] Release 2.0 must-have work items

Hi all, I'd like to start the VOTE for the must-have work items for release 2.0 [1]. The corresponding discussion thread is [2]. Please note that once the vote is approved, any changes to the must-have items (adding / removing must-have items, changing the priority) requires another vote.

[jira] [Created] (FLINK-32563) Allow connectors CI to specify the main supported Flink version

Etienne Chauchot created FLINK-32563: Summary: Allow connectors CI to specify the main supported Flink version Key: FLINK-32563 URL: https://issues.apache.org/jira/browse/FLINK-32563 Project:

Re: [DISCUSS] Release 2.0 Work Items

Thanks all for the discussion. The wiki has been updated as discussed. I'm starting a vote now. Best, Xintong On Wed, Jul 5, 2023 at 9:52 AM Xintong Song wrote: > Hi ConradJam, > > I think Chesnay has already put his name as the Contributor for the two > tasks you listed. Maybe you can

[jira] [Created] (FLINK-32562) FileSink Compactor Service should not use FileWriter from Sink for OutputStreamBasedFileCompactor

Shengnan YU created FLINK-32562: --- Summary: FileSink Compactor Service should not use FileWriter from Sink for OutputStreamBasedFileCompactor Key: FLINK-32562 URL: https://issues.apache.org/jira/browse/FLINK-32562

[jira] [Created] (FLINK-32561) Change the status field reconciliationTimestamp from long to Date

Xin Hao created FLINK-32561: --- Summary: Change the status field reconciliationTimestamp from long to Date Key: FLINK-32561 URL: https://issues.apache.org/jira/browse/FLINK-32561 Project: Flink

Re: [DISUCSS] Deprecate multiple APIs in 1.18

Thanks all for the discussion. I've created FLINK-32557 for this. Best, Xintong On Thu, Jul 6, 2023 at 1:00 AM Jing Ge wrote: > Hi Alex, > > > > > 3. remove SinkFunction. > > Which steps do you imply for the 1.18 release and for the 2.0 release? > > > > for 2.0 release. 1.18 will be

[jira] [Created] (FLINK-32560) Properly deprecate all Scala APIs

Xintong Song created FLINK-32560: Summary: Properly deprecate all Scala APIs Key: FLINK-32560 URL: https://issues.apache.org/jira/browse/FLINK-32560 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-32559) Deprecate Queryable State

Xintong Song created FLINK-32559: Summary: Deprecate Queryable State Key: FLINK-32559 URL: https://issues.apache.org/jira/browse/FLINK-32559 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-32558) Properly deprecate DataSet API

Xintong Song created FLINK-32558: Summary: Properly deprecate DataSet API Key: FLINK-32558 URL: https://issues.apache.org/jira/browse/FLINK-32558 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-32557) API deprecations in Flink 1.18

Xintong Song created FLINK-32557: Summary: API deprecations in Flink 1.18 Key: FLINK-32557 URL: https://issues.apache.org/jira/browse/FLINK-32557 Project: Flink Issue Type: Technical Debt

Re: [DISCUSS] FLIP-325: Support configuring end-to-end allowed latency

Hi Dong, Thanks for your clarification. > Actually, I think it could make sense to toggle isBacklog between true and > false while the job is running. > If isBacklog is toggled too often back and forth(e.g. by unexpected mistake, unstable system, etc), a large amount of RecordAttributes might

Re: [DISCUSS] FLIP-314: Support Customized Job Lineage Listener

Hi Shammon, Thanks for the update! Best regards, Jing On Fri, Jul 7, 2023 at 4:46 AM Shammon FY wrote: > Thanks Jing, sounds good to me. > > I have updated the FLIP and renamed the lineage related classes to > `LineageGraph`, `LineageVertex` and `LineageEdge` and keep it consistent > with the

Re: [DISCUSS] Flink and Externalized connectors leads to block and circular dependency problems

Hi all, I also agree with what's been said above. +1, I think the Table API delegation is a good suggestion--it essentially allows a connector to get Python support for free. We've seen that Table/SQL and Python APIs complement each other well and are ideal for data scientists. With respect to

[jira] [Created] (FLINK-32556) Renames contenderID into componentId

Matthias Pohl created FLINK-32556: - Summary: Renames contenderID into componentId Key: FLINK-32556 URL: https://issues.apache.org/jira/browse/FLINK-32556 Project: Flink Issue Type: Sub-task