[jira] [Created] (FLINK-14526) Support Hive version 1.1.0 and 1.1.1

Rui Li created FLINK-14526: -- Summary: Support Hive version 1.1.0 and 1.1.1 Key: FLINK-14526 URL: https://issues.apache.org/jira/browse/FLINK-14526 Project: Flink Issue Type: Task

[jira] [Created] (FLINK-14525) buffer pool is destroyed

Saqib created FLINK-14525: - Summary: buffer pool is destroyed Key: FLINK-14525 URL: https://issues.apache.org/jira/browse/FLINK-14525 Project: Flink Issue Type: Bug Components: Runtime /

Re: [VOTE] FLIP-78: Flink Python UDF Environment and Dependency Management

Hi Max, Is there any other concerns from your side? I appreciate if you can give some feedback and vote on this. Best, Wei > 在 2019年10月25日，09:33，jincheng sun 写道： > > Hi Thomas, > > Thanks for your explanation. I understand your original intention. I will > seriously consider this issue.

[jira] [Created] (FLINK-14524) PostgreSQL JDBC sink generates invalid SQL in upsert mode

Fawad Halim created FLINK-14524: --- Summary: PostgreSQL JDBC sink generates invalid SQL in upsert mode Key: FLINK-14524 URL: https://issues.apache.org/jira/browse/FLINK-14524 Project: Flink

Re: [VOTE] FLIP-78: Flink Python UDF Environment and Dependency Management

Hi Thomas, Thanks for your explanation. I understand your original intention. I will seriously consider this issue. After I have the initial solution, I will bring up a further discussion in Beam ML. Thanks for your voting. :) Best, Jincheng Thomas Weise 于2019年10月25日周五 上午7:32写道： > Hi

Re: [VOTE] FLIP-78: Flink Python UDF Environment and Dependency Management

Hi Jincheng, Yes, this topic can be further discussed on the Beam ML. The only reason I brought it up here is that it would be desirable from Beam Flink runner perspective for the artifact staging mechanism that you work on to be reusable. Stage 1 in Beam is also up to the runner, artifact

[jira] [Created] (FLINK-14523) Flink Stops Consuming from Kafka after Leader Election

James B. Fitzgerald created FLINK-14523: --- Summary: Flink Stops Consuming from Kafka after Leader Election Key: FLINK-14523 URL: https://issues.apache.org/jira/browse/FLINK-14523 Project: Flink

Re: [DISCUSS] Introduce a location-oriented two-stage query mechanism toimprove the queryable state.

Hi vino, +1 for improvement on queryable state feature. This reminds me of the state-processing-api module, which is very helpful when we analyze state in offline. However currently we don’t have many ways to know what is happening about the state inside a running application, which makes me

Intermittent No FileSystem found exception

Hi everyone, We are running a Batch job on flink that reads data from GCS and does some aggregation on this data. We are intermittently getting issue: `No filesystem found for scheme gs` We are running Beam version 2.15.0 with FlinkRunner, Flink version: 1.6.4 On remote debugging the task

[jira] [Created] (FLINK-14522) Adjust GC Cleaner for unsafe memory and Java 11

Andrey Zagrebin created FLINK-14522: --- Summary: Adjust GC Cleaner for unsafe memory and Java 11 Key: FLINK-14522 URL: https://issues.apache.org/jira/browse/FLINK-14522 Project: Flink Issue

[jira] [Created] (FLINK-14521) CoLocationGroup is not set into JobVertex if the stream node chained with others

Yun Gao created FLINK-14521: --- Summary: CoLocationGroup is not set into JobVertex if the stream node chained with others Key: FLINK-14521 URL: https://issues.apache.org/jira/browse/FLINK-14521 Project:

Re: [DISCUSS] FLIP-70 - Support Computed Column for Flink SQL

If we move "STORED" to future work section, it is still unclear that whether we should have an consensu on the design of "STORED"? 1) no consensus needed, we just put the design effort in the future part to continue the work if we want to support it in the future. So the vote on this FLIP dosen't

[jira] [Created] (FLINK-14520) Could not find a suitable table factory, but Factory is available

Miguel Serrano created FLINK-14520: -- Summary: Could not find a suitable table factory, but Factory is available Key: FLINK-14520 URL: https://issues.apache.org/jira/browse/FLINK-14520 Project: Flink

[jira] [Created] (FLINK-14519) Fail on invoking declineCheckpoint remotely

Jiayi Liao created FLINK-14519: -- Summary: Fail on invoking declineCheckpoint remotely Key: FLINK-14519 URL: https://issues.apache.org/jira/browse/FLINK-14519 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-14518) Generalize TM->RM payload

Chesnay Schepler created FLINK-14518: Summary: Generalize TM->RM payload Key: FLINK-14518 URL: https://issues.apache.org/jira/browse/FLINK-14518 Project: Flink Issue Type: Sub-task

Re: [DISUCSS] FLIP-80: Expression String Serializable and Deserializable

Thanks Jark and Timo for your explain. +1 to use SQL strings. Just took a look to calcite unparse, it really complex. Jark, yeah, The only thing need by ExpressionConverter is RelBuilder. Best, Jingsong Lee On Thu, Oct 24, 2019 at 5:09 PM Timo Walther wrote: > Hi Jark, > > +1 for your

Re: [DISUCSS] FLIP-80: Expression String Serializable and Deserializable

Thank you all, then I will update the design doc which should be pretty simple now... Best, Jark On Thu, 24 Oct 2019 at 17:09, Timo Walther wrote: > Hi Jark, > > +1 for your suggestion. I think it will simplify the design a lot if we > serialize all expressions as SQL strings and will avoid

Re: [DISCUSS] FLIP-70 - Support Computed Column for Flink SQL

Yes. I think it makes sense to move to "Future Work" section. Best, Jark On Thu, 24 Oct 2019 at 17:11, Kurt Young wrote: > +1 to move to a future section. By deleting it I mean remove from > the content describing the current processing procedure. > > Best, > Kurt > > > On Thu, Oct 24, 2019 at

[RESULT][VOTE] FLIP-65: New type inference for Table API UDFs

Hi everyone, the voting time for FLIP-65 has passed. There were 7 +1 votes, 6 of which are binding: - Aljoscha (binding) - Jark (binding) - Hequn (binding) - Jincheng (binding) - Xingcan (binding) - Rong (binding) - Jingsong (non-binding) There were no disapproving votes. Thus, FLIP-65 has

Re: [Discussion] FLIP-79 Flink Function DDL Support

Hi Peter, thanks for your proposal. I left some comments in the FLIP document. I agree with Terry that we can have a MVP in Flink 1.10 but should already discuss the bigger picture as a DDL string cannot be changed easily once released. In particular we should discuss how resources for

Re: [DISCUSS] FLIP-70 - Support Computed Column for Flink SQL

+1 to move to a future section. By deleting it I mean remove from the content describing the current processing procedure. Best, Kurt On Thu, Oct 24, 2019 at 5:01 PM Timo Walther wrote: > Having an MVP and a limited scope sounds good to me. But I would not > remove the STORED keyword entirely

Re: [DISUCSS] FLIP-80: Expression String Serializable and Deserializable

Hi Jark, +1 for your suggestion. I think it will simplify the design a lot if we serialize all expressions as SQL strings and will avoid duplicate parser code. Initially, I had concerns that there might be expressions in the future that cannot be represented in SQL. But currently I cannot

Re: [DISCUSS] FLIP-70 - Support Computed Column for Flink SQL

Having an MVP and a limited scope sounds good to me. But I would not remove the STORED keyword entirely from the document. It shows that we have a long-term vision. Instead of deleting this content, I would move it to a Outlook/Future Work section. Regards, Timo On 24.10.19 10:55, Jark Wu

Re: [DISUCSS] FLIP-80: Expression String Serializable and Deserializable

Thanks Jingsong, As discussed in Java Expression DSL, we are planning to drop the Java Expression string API. So I think we don’t have a plan to unify #1 and #2. And in the future, we may only have SQL parser to parse a string expression. The only thing to consider is, whether can all the

Re: [DISCUSS] Rename the SQL ANY type to OPAQUE type

Thanks everyone for the feedback! We have a clear favorite which is the RAW type. I will make sure that this change is applied to the Flink code base. Thanks again, Timo On 22.10.19 04:07, Terry Wang wrote: “OPAQUE” seems a little strange to me. + 1 for ‘RAW’. Best, Terry Wang

Re: [DISCUSS] FLIP-70 - Support Computed Column for Flink SQL

+1 to remove “STORED” related content. We can add them when user requires. Others looks good to me in general. Thanks, Jark > 在 2019年10月24日，14:58，Kurt Young 写道： > > Hi Danny, > > Thanks for preparing this design document. IMO It's a very useful > feature, especially combined with time

Re: [VOTE] FLIP-81: Executor-related new ConfigOptions

+1 （non-binding） vino yang 于2019年10月24日周四 下午4:06写道： > +1 (non-binding) > > Best, > Vino > > Yang Wang 于2019年10月23日周三 下午9:05写道： > > > We could benefit a lot from unifying the cli options and config options. > > > > +1(non-binding) > > > > Best, > > Yang > > > > Aljoscha Krettek 于2019年10月23日周三

Re: [VOTE] FLIP-81: Executor-related new ConfigOptions

+1 (non-binding) Best, Vino Yang Wang 于2019年10月23日周三 下午9:05写道： > We could benefit a lot from unifying the cli options and config options. > > +1(non-binding) > > Best, > Yang > > Aljoscha Krettek 于2019年10月23日周三 下午5:24写道： > > > +1 (binding) > > > > Aljoscha > > > > > On 23. Oct 2019, at 10:41,

[jira] [Created] (FLINK-14517) Handle escape characters for partition path

Jingsong Lee created FLINK-14517: Summary: Handle escape characters for partition path Key: FLINK-14517 URL: https://issues.apache.org/jira/browse/FLINK-14517 Project: Flink Issue Type:

[jira] [Created] (FLINK-14516) Remove non credit based network code

Piotr Nowojski created FLINK-14516: -- Summary: Remove non credit based network code Key: FLINK-14516 URL: https://issues.apache.org/jira/browse/FLINK-14516 Project: Flink Issue Type: Task

Re: [SURVEY] Dropping non Credit-based Flow Control

Hi, Thank you all for the feedback. I’ve created a ticket [1] to remove the non Credit-based Flow Control code paths. Piotrek [1] https://issues.apache.org/jira/browse/FLINK-14516 > On 23 Oct 2019, at 10:59, Nico Kruber wrote: > > +1 > >

Re: [DISCUSS] FLIP-70 - Support Computed Column for Flink SQL

Hi Danny, Thanks for preparing this design document. IMO It's a very useful feature, especially combined with time attribute support to specify watermark in DDL. The design doc looks quite good, but I would suggest to reduce the scope of the first version. Like we don't have to support "STORED"

Re: [DISCUSS] FLIP-75: Flink Web UI Improvement Proposal

Hi all, I have updated the backend design in FLIP-75 . Here are some brief introductions: - Add metric for manage memory FLINK-14406 . -