[jira] [Created] (FLINK-21631) Add CountTrigger for Python group window aggregation

Huang Xingbo created FLINK-21631: Summary: Add CountTrigger for Python group window aggregation Key: FLINK-21631 URL: https://issues.apache.org/jira/browse/FLINK-21631 Project: Flink Issue

[jira] [Created] (FLINK-21630) Support Python UDAF in Session Window

Huang Xingbo created FLINK-21630: Summary: Support Python UDAF in Session Window Key: FLINK-21630 URL: https://issues.apache.org/jira/browse/FLINK-21630 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-21629) Support Python UDAF in Sliding Window

Huang Xingbo created FLINK-21629: Summary: Support Python UDAF in Sliding Window Key: FLINK-21629 URL: https://issues.apache.org/jira/browse/FLINK-21629 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-21628) Support Python UDAF in Tumbling Window

Huang Xingbo created FLINK-21628: Summary: Support Python UDAF in Tumbling Window Key: FLINK-21628 URL: https://issues.apache.org/jira/browse/FLINK-21628 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-21627) When you insert multiple inserts with statementSet, you modify multiple inserts with OPTIONS('table-name '=' XXX '), but only the first one takes effect

wangtaiyang created FLINK-21627: --- Summary: When you insert multiple inserts with statementSet, you modify multiple inserts with OPTIONS('table-name '=' XXX '), but only the first one takes effect Key: FLINK-21627

[jira] [Created] (FLINK-21626) Consider shaping newly introduced RuntimeContext.getJobId to return JobID with no Optional wrapper

Kezhu Wang created FLINK-21626: -- Summary: Consider shaping newly introduced RuntimeContext.getJobId to return JobID with no Optional wrapper Key: FLINK-21626 URL: https://issues.apache.org/jira/browse/FLINK-21626

[DISCUSS] FLIP-162 follow-up discussion

Hi, all As the FLIP-162 discussed, we agreed current time functions’ behavior is incorrect and plan to introduce the option table.exec.fallback-legacy-time-function to enable user fallback to incorrect behavior. (1) The option is convenient for users who want to upgrade to 1.13 but don't

[jira] [Created] (FLINK-21625) 5.03.2021 Benchmarks are not compiling

Piotr Nowojski created FLINK-21625: -- Summary: 5.03.2021 Benchmarks are not compiling Key: FLINK-21625 URL: https://issues.apache.org/jira/browse/FLINK-21625 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-21624) Correct FLOOR/CEIL (TIMESTAMP/TIMESTAMP_LTZ/DATE TO WEEK) functions

Leonard Xu created FLINK-21624: -- Summary: Correct FLOOR/CEIL (TIMESTAMP/TIMESTAMP_LTZ/DATE TO WEEK) functions Key: FLINK-21624 URL: https://issues.apache.org/jira/browse/FLINK-21624 Project: Flink

[jira] [Created] (FLINK-21623) Introduce CURRENT_ROW_TIMESTAMP function

Leonard Xu created FLINK-21623: -- Summary: Introduce CURRENT_ROW_TIMESTAMP function Key: FLINK-21623 URL: https://issues.apache.org/jira/browse/FLINK-21623 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-21622) Introduce function TO_TIMESTAMP_LTZ(numeric [, precision])

Leonard Xu created FLINK-21622: -- Summary: Introduce function TO_TIMESTAMP_LTZ(numeric [, precision]) Key: FLINK-21622 URL: https://issues.apache.org/jira/browse/FLINK-21622 Project: Flink

[jira] [Created] (FLINK-21621) Support TIMESTAMP_LTZ arithmetic

Leonard Xu created FLINK-21621: -- Summary: Support TIMESTAMP_LTZ arithmetic Key: FLINK-21621 URL: https://issues.apache.org/jira/browse/FLINK-21621 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-21620) [table-planner/table-parser] Support abbreviation TIMESTAMP_LTZ FOR TIMESTAMP WITH LOCAL TIME ZONE

Leonard Xu created FLINK-21620: -- Summary: [table-planner/table-parser] Support abbreviation TIMESTAMP_LTZ FOR TIMESTAMP WITH LOCAL TIME ZONE Key: FLINK-21620 URL: https://issues.apache.org/jira/browse/FLINK-21620

Re: Re: Re: [DISCUSS] FLIP-147: Support Checkpoints After Tasks Finished

Hi Piotr, Very thanks for the suggestions and thoughts! > Is this a problem? Pipeline would be empty, so EndOfPartitionEvent would be > traveling very quickly. No, this is not a problem, sorry I have some wrong thoughts here, initially in fact I'm thinking on this issue raised by @kezhu: >

[jira] [Created] (FLINK-21619) Remove the optional host and webui-port in jobmanager.sh and use common args instead

Yang Wang created FLINK-21619: - Summary: Remove the optional host and webui-port in jobmanager.sh and use common args instead Key: FLINK-21619 URL: https://issues.apache.org/jira/browse/FLINK-21619

[jira] [Created] (FLINK-21618) Introduce a new integration test framework for SQL Client

Jark Wu created FLINK-21618: --- Summary: Introduce a new integration test framework for SQL Client Key: FLINK-21618 URL: https://issues.apache.org/jira/browse/FLINK-21618 Project: Flink Issue Type:

[jira] [Created] (FLINK-21617) FLIP-162: Consistent Flink SQL time function behavior

Leonard Xu created FLINK-21617: -- Summary: FLIP-162: Consistent Flink SQL time function behavior Key: FLINK-21617 URL: https://issues.apache.org/jira/browse/FLINK-21617 Project: Flink Issue

[jira] [Created] (FLINK-21616) Introduce a new integration test framework for SQL Client

Jark Wu created FLINK-21616: --- Summary: Introduce a new integration test framework for SQL Client Key: FLINK-21616 URL: https://issues.apache.org/jira/browse/FLINK-21616 Project: Flink Issue Type:

[RESULT][VOTE] FLIP-162: Consistent Flink SQL time function behavior

Hi all, The voting time for FLIP-162 has passed. I'm closing the vote now. There were 4 +1 votes, 4 of which are binding: - Jark (binding) - Timo (binding) - Kurt (binding) - Jingsong (binding) There were no -1 votes, thus, FLIP-162 has been accepted. Thanks everyone! Best, Leonard

[jira] [Created] (FLINK-21614) Introduce a new integration test framework for SQL Client

Jark Wu created FLINK-21614: --- Summary: Introduce a new integration test framework for SQL Client Key: FLINK-21614 URL: https://issues.apache.org/jira/browse/FLINK-21614 Project: Flink Issue Type:

[jira] [Created] (FLINK-21615) Introduce a new integration test framework for SQL Client

Jark Wu created FLINK-21615: --- Summary: Introduce a new integration test framework for SQL Client Key: FLINK-21615 URL: https://issues.apache.org/jira/browse/FLINK-21615 Project: Flink Issue Type:

[DISCUSSION] Introduce a separated memory pool for the TM merge shuffle

Hi, all In the Flink 1.12 we introduce the TM merge shuffle. But the out-of-the-box experience of using TM merge shuffle is not very good. The main reason is that the default configuration always makes users encounter OOM [1]. So we hope to introduce a managed memory pool for TM merge shuffle to

[jira] [Created] (FLINK-21613) Parse Compute Column with `IN` expression throws NPE

Shuo Cheng created FLINK-21613: -- Summary: Parse Compute Column with `IN` expression throws NPE Key: FLINK-21613 URL: https://issues.apache.org/jira/browse/FLINK-21613 Project: Flink Issue Type:

[jira] [Created] (FLINK-21612) Support StreamExecGroupAggregate json serialization/deserialization

godfrey he created FLINK-21612: -- Summary: Support StreamExecGroupAggregate json serialization/deserialization Key: FLINK-21612 URL: https://issues.apache.org/jira/browse/FLINK-21612 Project: Flink

Re: [DISCUSS] FLIP-165: Operator's Flame Graphs

@Till, I've added the proposed ThreadInfoSamplesRequest and updated the FLIP and the PR accordingly. Best, -- Alexander Fedulov | Solutions Architect Follow us @VervericaData -- Join Flink Forward - The Apache Flink Conference

[jira] [Created] (FLINK-21611) Japicmp fails with "Could not resolve org.apache.flink:flink-core:jar:1.12.0"

Dawid Wysakowicz created FLINK-21611: Summary: Japicmp fails with "Could not resolve org.apache.flink:flink-core:jar:1.12.0" Key: FLINK-21611 URL: https://issues.apache.org/jira/browse/FLINK-21611

[jira] [Created] (FLINK-21610) ProcessFailureCancelingITCase failed on azure

Dawid Wysakowicz created FLINK-21610: Summary: ProcessFailureCancelingITCase failed on azure Key: FLINK-21610 URL: https://issues.apache.org/jira/browse/FLINK-21610 Project: Flink Issue

[jira] [Created] (FLINK-21609) SimpleRecoveryITCaseBase.testRestartMultipleTimes fails on azure

Dawid Wysakowicz created FLINK-21609: Summary: SimpleRecoveryITCaseBase.testRestartMultipleTimes fails on azure Key: FLINK-21609 URL: https://issues.apache.org/jira/browse/FLINK-21609 Project:

[jira] [Created] (FLINK-21608) YARNHighAvailabilityITCase.testClusterClientRetrieval fails with "There is at least one application..."

Dawid Wysakowicz created FLINK-21608: Summary: YARNHighAvailabilityITCase.testClusterClientRetrieval fails with "There is at least one application..." Key: FLINK-21608 URL:

Re: [VOTE] FLIP-151: Incremental snapshots for heap-based state backend

+1 (binding) The latest FLIP document LGTM. Thanks for driving this Roman! Best Regards, Yu On Thu, 4 Mar 2021 at 18:24, David Anderson wrote: > +1 (non-binding) > > On Mon, Mar 1, 2021 at 10:12 AM Roman Khachatryan > wrote: > > > Hi everyone, > > > > since the discussion [1] about FLIP-151

[jira] [Created] (FLINK-21607) Twitter table source connector

Jeff Zhang created FLINK-21607: -- Summary: Twitter table source connector Key: FLINK-21607 URL: https://issues.apache.org/jira/browse/FLINK-21607 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-21606) TaskManager connected to invalid JobManager leading to TaskSubmissionException

Robert Metzger created FLINK-21606: -- Summary: TaskManager connected to invalid JobManager leading to TaskSubmissionException Key: FLINK-21606 URL: https://issues.apache.org/jira/browse/FLINK-21606

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

big +1 from my side. Best, Jark On Thu, 4 Mar 2021 at 20:59, Leonard Xu wrote: > +1 for the roadmap. > > Thanks Timo for driving this. > > Best, > Leonard > > > 在 2021年3月4日，20:40，Timo Walther 写道： > > > > Last call for feedback on this topic. > > > > It seems everyone agrees to finally

Re: Re: Re: [DISCUSS] FLIP-147: Support Checkpoints After Tasks Finished

Hi Yun and Kezhu, > 1. We might introduce a new type of event to notify the endOfInput() though the graph first, and then A/B waits for the final checkpoint, then A emit EndOfPartitionEvent to exit all the tasks as now. As I mentioned in one of the PRs, I would opt for this solution. > if we

[jira] [Created] (FLINK-21605) Uniform the format of property name in the flink configuration file.

张超明 created FLINK-21605: --- Summary: Uniform the format of property name in the flink configuration file. Key: FLINK-21605 URL: https://issues.apache.org/jira/browse/FLINK-21605 Project: Flink Issue

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

+1 for the roadmap. Thanks Timo for driving this. Best, Leonard > 在 2021年3月4日，20:40，Timo Walther 写道： > > Last call for feedback on this topic. > > It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been > accepted for a very long time, I think we don't need another

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

Last call for feedback on this topic. It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been accepted for a very long time, I think we don't need another voting thread for executing the last implementation step. Please let me know if you think differently. I will start

[jira] [Created] (FLINK-21604) Remove adaptive scheduler nightly test profile, replace with more specific testing approach

Robert Metzger created FLINK-21604: -- Summary: Remove adaptive scheduler nightly test profile, replace with more specific testing approach Key: FLINK-21604 URL: https://issues.apache.org/jira/browse/FLINK-21604

[jira] [Created] (FLINK-21603) SQLClientKafkaITCase failed due to unexpected end of file

Yun Tang created FLINK-21603: Summary: SQLClientKafkaITCase failed due to unexpected end of file Key: FLINK-21603 URL: https://issues.apache.org/jira/browse/FLINK-21603 Project: Flink Issue

Re: [VOTE] FLIP-151: Incremental snapshots for heap-based state backend

+1 (non-binding) On Mon, Mar 1, 2021 at 10:12 AM Roman Khachatryan wrote: > Hi everyone, > > since the discussion [1] about FLIP-151 [2] seems to have reached a > consensus, I'd like to start a formal vote for the FLIP. > > Please vote +1 to approve the FLIP, or -1 with a comment. The vote will

Re: Re: Re: [DISCUSS] FLIP-147: Support Checkpoints After Tasks Finished

Hi Piotrek, For “end-flushing”, I presented no new candidates. I uses “end-flushing” to avoid naming issues. It should be “close” in allowing checkpoint after “close” while “endOfInput” in your approach. What I tried to express is we can do some backporting work to mitigate possible breaking

[jira] [Created] (FLINK-21602) Creation of ExecutionGraph happens in main thread

Till Rohrmann created FLINK-21602: - Summary: Creation of ExecutionGraph happens in main thread Key: FLINK-21602 URL: https://issues.apache.org/jira/browse/FLINK-21602 Project: Flink Issue

Re: Re: Re: [DISCUSS] FLIP-147: Support Checkpoints After Tasks Finished

Hi all, Very thanks for all the discussions! Regarding the operator API on exit, I'm also glad that we are reaching consistency roughly. Based on the previous discussions I'm also support doing the final checkpoint after the previous "close" method, and we rename these methods to make them

Re: Re: Re: [DISCUSS] FLIP-147: Support Checkpoints After Tasks Finished

Hi Kezhu, What do you mean by “end-flushing”? I was suggesting to just keep `endOfInput()` and `dispose()`. Are you suggesting to have a one `endFlushing()` method, that is called after quiescing timers/mailbox, but before final checkpoint and `dispose()`? Are we sure we really need this extra

[jira] [Created] (FLINK-21601) observing errors in jobmanager - after created prometheus metric reporter

Bhagi created FLINK-21601: - Summary: observing errors in jobmanager - after created prometheus metric reporter Key: FLINK-21601 URL: https://issues.apache.org/jira/browse/FLINK-21601 Project: Flink