[jira] [Created] (FLINK-8841) Duplicate MapSerializer and HashMapSerializer.

Kostas Kloudas created FLINK-8841: - Summary: Duplicate MapSerializer and HashMapSerializer. Key: FLINK-8841 URL: https://issues.apache.org/jira/browse/FLINK-8841 Project: Flink Issue Type:

Re: Verifying watermarks in integration test

Hi, I had sorted out how to run the topology in embedded mode. What wasn't clear to me is how I can verify the watermark, but as per following thread that can be done by inserting a process function:

Re: Proposal - Change shard discovery in Flink Kinesis Connector to use ListShards

It will be good to be able to use the ListShards API. Are there any concerns bumping up the AWS SDK dependency? I see it was last done in https://issues.apache.org/jira/browse/FLINK-7422 Thanks On Wed, Feb 28, 2018 at 10:38 PM, Kailash Dayanand wrote: > Based on the

Re: [DISCUSS] Convert main Table API classes into traits

Hi Timo, Thanks for looking into this Timo. It's becoming increasingly messy for my trying to locate the correct functions in IDE :-/ This is probably due to the fact that Scala and Java access modifiers / qualifiers are subtly and fundamentally different. Using Trait might be the best solution

[jira] [Created] (FLINK-8842) Change default REST port to 8081

Till Rohrmann created FLINK-8842: Summary: Change default REST port to 8081 Key: FLINK-8842 URL: https://issues.apache.org/jira/browse/FLINK-8842 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-8843) Decouple bind REST address from advertised address

Till Rohrmann created FLINK-8843: Summary: Decouple bind REST address from advertised address Key: FLINK-8843 URL: https://issues.apache.org/jira/browse/FLINK-8843 Project: Flink Issue Type:

Re: [DISCUSS] Convert main Table API classes into traits

Hi Timo, I am throwing some second thoughts here, as I don't quite see what trait provides over abstract class here for TableEnvironment case. Trait in scala can also have implementation and you can have 'private[flink]' or 'protected' type and method in trait as well. AFAIK, the differences

[jira] [Created] (FLINK-8844) Export job jar file name or job version property via REST API

Elias Levy created FLINK-8844: - Summary: Export job jar file name or job version property via REST API Key: FLINK-8844 URL: https://issues.apache.org/jira/browse/FLINK-8844 Project: Flink Issue

Re: [DISCUSS] Convert main Table API classes into traits

Hi Shuyi, I am already assuming all package private and protected modifiers will be cleaned up and moved to internal implementation. Please correct me if I were wrong, Timo. Thanks, Rong On Fri, Mar 2, 2018, 5:02 PM Shuyi Chen wrote: > Hi Timo, > > I am throwing some

Re: [DISCUS] Flink SQL Client dependency management

Hi everyone, thanks for your opinions. So the majority voted for option (2) fat jars that are ready to be used. I will create an Jira issue and prepare the infrastructure for the first connector and first format. Regards, Timo Am 3/1/18 um 11:38 AM schrieb Fabian Hueske: I agree, option

[jira] [Created] (FLINK-8831) Create SQL Client dependencies

Timo Walther created FLINK-8831: --- Summary: Create SQL Client dependencies Key: FLINK-8831 URL: https://issues.apache.org/jira/browse/FLINK-8831 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-8834) Job fails to restart due to some tasks stuck in cancelling state

Daniel Harper created FLINK-8834: Summary: Job fails to restart due to some tasks stuck in cancelling state Key: FLINK-8834 URL: https://issues.apache.org/jira/browse/FLINK-8834 Project: Flink

StreamSQL queriable state

Hi guys, I am checking out the queriable state API, and it seems that most of the tooling is already available. However, the queriable state is available just for the streaming API, not at the StreamSQL API level. In principle, as the flink-table is aware of the query semantic and data output

[jira] [Created] (FLINK-8833) Create SQL Client JSON format fat-jar

Timo Walther created FLINK-8833: --- Summary: Create SQL Client JSON format fat-jar Key: FLINK-8833 URL: https://issues.apache.org/jira/browse/FLINK-8833 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-8830) YarnResourceManager throws NullPointerException

Piotr Nowojski created FLINK-8830: - Summary: YarnResourceManager throws NullPointerException Key: FLINK-8830 URL: https://issues.apache.org/jira/browse/FLINK-8830 Project: Flink Issue Type:

Re: Checkpointing Event Time Watermarks

Hi Xingcan We are receiving events from a no. of independent data sources and hence, data arriving into our Flink topology (via Kafka) would be out of order. We are creating 1-min event time windows in our Flink topology and generating event time watermarks as (current event time - some

Re: StreamSQL queriable state

Hi Renjie, that would be great. There is already a Jira issue for it: https://issues.apache.org/jira/browse/FLINK-6968 Feel free to assign it to yourself. You can reuse parts of my code if you want. But maybe it would make sense to have a little design document first about what we want to

Re: StreamSQL queriable state

Hi, Timo: It seems that I can't assign it to myself. Could you please help to assign that to me? My jira username is liurenjie1024 and my email is liurenjie2...@gmail.com On Fri, Mar 2, 2018 at 6:24 PM Timo Walther wrote: > Hi Renjie, > > that would be great. There is

[jira] [Created] (FLINK-8836) Duplicating a KryoSerializer does not duplicate registered default serializers

Tzu-Li (Gordon) Tai created FLINK-8836: -- Summary: Duplicating a KryoSerializer does not duplicate registered default serializers Key: FLINK-8836 URL: https://issues.apache.org/jira/browse/FLINK-8836

Re: StreamSQL queriable state

Hi, Timo, I've been planning on the same thing and would like to contribute that. On Fri, Mar 2, 2018 at 6:05 PM Timo Walther wrote: > Hi Stefano, > > yes there are plan in this direction. Actually, I already worked on such > a QueryableStateTableSink [1] in the past but

Re: StreamSQL queriable state

Great, thank you. I'll start by writing a design doc. On Fri, Mar 2, 2018 at 6:40 PM Timo Walther wrote: > I gave you contributor permissions in Jira. You should be able to assign > it to yourself now. > > Am 3/2/18 um 11:33 AM schrieb Renjie Liu: > > Hi, Timo: > > It seems

[jira] [Created] (FLINK-8835) Fix TaskManager config keys

Stephan Ewen created FLINK-8835: --- Summary: Fix TaskManager config keys Key: FLINK-8835 URL: https://issues.apache.org/jira/browse/FLINK-8835 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-8837) Move DataStreamUtils to package 'experimental'.

Stephan Ewen created FLINK-8837: --- Summary: Move DataStreamUtils to package 'experimental'. Key: FLINK-8837 URL: https://issues.apache.org/jira/browse/FLINK-8837 Project: Flink Issue Type: Bug

Re: StreamSQL queriable state

Hi Stefano, yes there are plan in this direction. Actually, I already worked on such a QueryableStateTableSink [1] in the past but never finished it because of priority shifts. Would be great if somebody wants to contribute this functionality :) Regards, Timo [1]

Re: StreamSQL queriable state

I gave you contributor permissions in Jira. You should be able to assign it to yourself now. Am 3/2/18 um 11:33 AM schrieb Renjie Liu: Hi, Timo: It seems that I can't assign it to myself. Could you please help to assign that to me? My jira username is liurenjie1024 and my email is

[jira] [Created] (FLINK-8839) Table source factory discovery is broken in SQL Client

Timo Walther created FLINK-8839: --- Summary: Table source factory discovery is broken in SQL Client Key: FLINK-8839 URL: https://issues.apache.org/jira/browse/FLINK-8839 Project: Flink Issue

[jira] [Created] (FLINK-8840) Pull out YarnClient initialization out of AbstractYarnClusterDescriptor

Till Rohrmann created FLINK-8840: Summary: Pull out YarnClient initialization out of AbstractYarnClusterDescriptor Key: FLINK-8840 URL: https://issues.apache.org/jira/browse/FLINK-8840 Project: Flink

RE: StreamSQL queriable state

Hi Timo, Renjie, What I was thinking did not include the QueryableStateTableSink, but rather tap in directly into the state of a streaming operator. Perhaps it is the same thing, but just it sounds not intuitive to consider it a sink. So, we would need a way to configure the environment for

[jira] [Created] (FLINK-8838) Add Support UNNEST a MultiSet type field

lincoln.lee created FLINK-8838: -- Summary: Add Support UNNEST a MultiSet type field Key: FLINK-8838 URL: https://issues.apache.org/jira/browse/FLINK-8838 Project: Flink Issue Type: New Feature