[jira] [Created] (FLINK-20996) Using a cryptographically weak Pseudo Random Number Generator (PRNG)

2021-01-15 Thread Ya Xiao (Jira)
Ya Xiao created FLINK-20996: --- Summary: Using a cryptographically weak Pseudo Random Number Generator (PRNG) Key: FLINK-20996 URL: https://issues.apache.org/jira/browse/FLINK-20996 Project: Flink I

[jira] [Created] (FLINK-20995) Calling execute() on org.apache.flink.table.api.Table Throws Exception

2021-01-15 Thread Robert Cullen (Jira)
Robert Cullen created FLINK-20995: - Summary: Calling execute() on org.apache.flink.table.api.Table Throws Exception Key: FLINK-20995 URL: https://issues.apache.org/jira/browse/FLINK-20995 Project: Fli

[jira] [Created] (FLINK-20994) Add public method to create TableEnvironment in PyFlink

2021-01-15 Thread Seth Wiesman (Jira)
Seth Wiesman created FLINK-20994: Summary: Add public method to create TableEnvironment in PyFlink Key: FLINK-20994 URL: https://issues.apache.org/jira/browse/FLINK-20994 Project: Flink Issue

Re: outdated version of com.esotericsoftware.kryo

2021-01-15 Thread Seth Wiesman
To expand on Till's answer, Flink uses Kryo whenever the type system does not recognize a given type. If your job works with Kryo fallback disabled, there should be no usage of Kryo serialization in your snapshots[1]. In theory, it should be possible to upgrade Kryo using Flink's schema migration c

Re: outdated version of com.esotericsoftware.kryo

2021-01-15 Thread Till Rohrmann
Yes, I think that Flink uses whatever key-/value-serializer is defined for serializing the keys/values for a savepoint. I haven't looked in detail into the problem but if Kryo offers some migration options, then this could make the problem a bit easier. Cheers, Till On Fri, Jan 15, 2021 at 2:4

Re: [DISCUSS] FLIP-157 Migrate Flink Documentation from Jekyll to Hugo

2021-01-15 Thread Seth Wiesman
Great, if there aren't any other concerns I will open this up for a vote on Monday. Seth On Thu, Jan 14, 2021 at 9:03 AM Seth Wiesman wrote: > Happy to see there is enthusiasm for this change, let me try and answers > each of these questions. > > @Jark Wu Hugo has proper support for i18n which

[VOTE] FLIP-147: Support Checkpoint After Tasks Finished

2021-01-15 Thread Yun Gao
Hi all, I would like to start the vote for FLIP-147[1], which propose to support checkpoints after tasks finished and is discussed in [2]. The vote will last at least 72 hours (Jan 20th due to weekend), following the consensus voting process. thanks, Yun [1] https://cwiki.apache.org/conflu

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

2021-01-15 Thread Yun Gao
Hi Aljoscha, I think so since we seems to do not have other divergence and new objections now. I'll open the vote then. Very thanks! Best, Yun -- From:Aljoscha Krettek Send Time:2021 Jan. 15 (Fri.) 21:24 To:dev Subject:Re:

Re: outdated version of com.esotericsoftware.kryo

2021-01-15 Thread Niels Basjes
Till, So, we save the savepoints using the Kryo native format? But I see that Kryo 2.24 (as mentioned here) is from may 2014 ... that's ... really old ! https://github.com/EsotericSoftware/kryo/releases/tag/kryo-2.24.0 I see that Kryo has some suggestions on the migration options: https://github.

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

2021-01-15 Thread Aljoscha Krettek
Thanks for the summary! I think we can now move towards a [VOTE] thread, right? On 2021/01/15 13:43, Yun Gao wrote: 1) For the problem that the "new" root task coincidently finished before getting triggered successfully, we have listed two options in the FLIP-147[1], for the first version, now

Re: outdated version of com.esotericsoftware.kryo

2021-01-15 Thread Till Rohrmann
Hi Fred, one reason why this hasn't been updated is that Flink needs to ensure backwards compatibility. Hence, if the newer Kryo library serializes objects differently, then Flink would need to migrate old savepoints having been stored via the old Kryo serializer to the new format. This is current

[jira] [Created] (FLINK-20993) Cleaning up checkpoint during shutdown may fail JM

2021-01-15 Thread Roman Khachatryan (Jira)
Roman Khachatryan created FLINK-20993: - Summary: Cleaning up checkpoint during shutdown may fail JM Key: FLINK-20993 URL: https://issues.apache.org/jira/browse/FLINK-20993 Project: Flink

[jira] [Created] (FLINK-20992) Checkpoint cleanup can kill JobMaster

2021-01-15 Thread Till Rohrmann (Jira)
Till Rohrmann created FLINK-20992: - Summary: Checkpoint cleanup can kill JobMaster Key: FLINK-20992 URL: https://issues.apache.org/jira/browse/FLINK-20992 Project: Flink Issue Type: Bug

[DISCUSS] Dealing with deprecated and legacy code in Flink

2021-01-15 Thread Timo Walther
Hi everyone, I would like to start a discussion how we treat deprecated and legacy code in Flink in the future. During the last years, our code base has grown quite a bit and a couple of interfaces and components have been reworked on the way. I'm sure each component has a few legacy parts t

[jira] [Created] (FLINK-20991) Create 1.12.1 official image

2021-01-15 Thread Xintong Song (Jira)
Xintong Song created FLINK-20991: Summary: Create 1.12.1 official image Key: FLINK-20991 URL: https://issues.apache.org/jira/browse/FLINK-20991 Project: Flink Issue Type: Task Compo

outdated version of com.esotericsoftware.kryo

2021-01-15 Thread Teunissen, F.G.J. (Fred)
Hi, While I was resolving a dependency version conflict in our project that uses Flink v1.11.2 I noticed that Flink is using the library ‘com.esotericsoftware.kryo:kryo:2.24.0’. Is there a reason why this library isn’t updated to

[jira] [Created] (FLINK-20990) Service account property ignored for Kubernetes Standalone deployment

2021-01-15 Thread Damian G (Jira)
Damian G created FLINK-20990: Summary: Service account property ignored for Kubernetes Standalone deployment Key: FLINK-20990 URL: https://issues.apache.org/jira/browse/FLINK-20990 Project: Flink

Re: [DISCUSS][FLINK-20726] Introduce Pulsar connector

2021-01-15 Thread Till Rohrmann
Hi Jianyun, I've assigned you to the respective tickets. Cheers, Till On Thu, Jan 14, 2021 at 9:07 PM 赵 建云 wrote: > Hi Arvid, > > Thank you very much for being a mentor to the Flink community, I will > finish submitting all the content as soon as possible. > > The PR submission will be support

Re: [DISCUSS] Support obtaining Hive delegation tokens when submitting application to Yarn

2021-01-15 Thread Rui Li
Thanks Jie for driving this discussion. I also prefer a pluggable delegation token provider. And I think users can use configurations to specify the hive conf path, similar to how users specify a hive catalog. On Wed, Jan 13, 2021 at 4:51 PM Till Rohrmann wrote: > Hi Jie Wang, > > thanks for sta

Re: [Discussion] More Deep Learning usages on Apache Flink

2021-01-15 Thread Qing Lan
Hi Becket, Talking about the IPC, DJL is leveraging the JNI/JNA directly to connect to DL engines C /C++ API. So the latency between C++ and Java is minimum (~10ns). Performance wise speaking, DJL can offers true multi threading Java inference, means load model once, use in as many threads you

Re: [DISCUSS] Releasing Apache Flink 1.10.3

2021-01-15 Thread Xintong Song
Hi all, Seems there's no objections. Then I'm managing this release. Since the build is stable, and CVE-2020-17518 is already ported to the 1.10 branch, it looks like we can prepare the release candidate anytime. I'd like to leave a bit more time for people to report issues that they want to inc