[jira] [Created] (FLINK-18714) Support consuming multiple topics for KafkaTableSource

hailong wang created FLINK-18714: Summary: Support consuming multiple topics for KafkaTableSource Key: FLINK-18714 URL: https://issues.apache.org/jira/browse/FLINK-18714 Project: Flink Issue

[jira] [Created] (FLINK-18713) Allow default ms unit for table.exec.mini-batch.allow-latency etc.

hailong wang created FLINK-18713: Summary: Allow default ms unit for table.exec.mini-batch.allow-latency etc. Key: FLINK-18713 URL: https://issues.apache.org/jira/browse/FLINK-18713 Project: Flink

[jira] [Created] (FLINK-18712) Flink RocksDB statebackend memory leak issue

Farnight created FLINK-18712: Summary: Flink RocksDB statebackend memory leak issue Key: FLINK-18712 URL: https://issues.apache.org/jira/browse/FLINK-18712 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-18711) Trim the blank space for TableOptions

hailong wang created FLINK-18711: Summary: Trim the blank space for TableOptions Key: FLINK-18711 URL: https://issues.apache.org/jira/browse/FLINK-18711 Project: Flink Issue Type:

[jira] [Created] (FLINK-18710) ResourceProfileInfo is not serializable

Till Rohrmann created FLINK-18710: - Summary: ResourceProfileInfo is not serializable Key: FLINK-18710 URL: https://issues.apache.org/jira/browse/FLINK-18710 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-18709) Implement PhysicalSlotProvider

Andrey Zagrebin created FLINK-18709: --- Summary: Implement PhysicalSlotProvider Key: FLINK-18709 URL: https://issues.apache.org/jira/browse/FLINK-18709 Project: Flink Issue Type: Sub-task

[Discuss] Handling of Timestamp in DataGen table created via LIKE

Hi everyone, Currently, the data gen table source only supports a subset of Flink SQL types. One missing type in particular is TIMESTAMP(3). The reason, I suspect, it was not added originally is that it doesn't really make sense to have random timestamps. What you really want is for them to be

[jira] [Created] (FLINK-18708) The links of the connector sql jar of Kafka 0.10 and 0.11 are extinct

Huang Xingbo created FLINK-18708: Summary: The links of the connector sql jar of Kafka 0.10 and 0.11 are extinct Key: FLINK-18708 URL: https://issues.apache.org/jira/browse/FLINK-18708 Project: Flink

Re: Functions in Flick

Hi David, 1. Here's an example on how to deploy Stateful Functions on Kubernetes: https://github.com/apache/flink-statefun/tree/master/statefun-examples/statefun-python-k8s-example You don't need to install anything in a serverless environment for using it. 2. Since the underlying processing

Re: Inconsistent behavior between different states with ListState.get().iterator().remove()

Thanks for the response, filed https://issues.apache.org/jira/browse/FLINK-18707 as a minor bug. — Ken > On Jul 24, 2020, at 2:03 AM, Aljoscha Krettek wrote: > > That is a very good observation! > > In an ideal world, I would say we

Re: [VOTE] FLIP-129: Refactor Descriptor API to register connector in Table API

+1 Thanks for driving this Jark. Regards, Timo On 24.07.20 12:42, Jark Wu wrote: Hi all, I would like to start the vote for FLIP-129 [1], which is discussed and reached consensus in the discussion thread [2]. The vote will be open until 27th July (72h), unless there is an objection or not

Re: [DISCUSS] Adding Azure Platform Support in DataStream, Table and SQL Connectors

Great! Looking forward to your first pull request. I agree that having a connector in Flink's codebase will probably help it's adoption. However, we are careful with the connectors we are adding to Flink for the following reasons: a) The Flink project is lacking people to maintain all connectors,

[jira] [Created] (FLINK-18707) Calling remove() for RockDB ListState iterator does nothing

Kenneth William Krugler created FLINK-18707: --- Summary: Calling remove() for RockDB ListState iterator does nothing Key: FLINK-18707 URL: https://issues.apache.org/jira/browse/FLINK-18707

Re: Hi

Hi Dev Team/Yangez, I am following the commands to unzip and execute in windows command line : $ cd ~/Downloads# Go to download directory$ tar xzf flink-*.tgz # Unpack the downloaded archive$ cd flink-1.9.0 $ ./bin/start-cluster.sh # Start Flink Cluster is starting in github but

Re: [DISCUSS] FLIP-130: Support for Python DataStream API (Stateless Part)

Hi David, Thank you for your reply! I have started the vote for this FLIP, but we can keep the discussion on this thread. In my perspective, I would not against adding the DataStream.partitionCustom to Python DataStream API. However, more inputs are welcomed. Best, Shuiqiang David Anderson

[VOTE] FLIP-130: Support for Python DataStream API (Stateless Part)

Hi everyone, I would like to start the vote for FLIP-130[1], which is discussed and reached a consensus through the discussion thread[2]. The vote will be open until 29th July (72h), unless there is an objection or not enough votes. Best, Shuiqiang [1]:

Re: [DISCUSS] FLIP-130: Support for Python DataStream API (Stateless Part)

Sorry I'm coming to this rather late, but I would like to argue that DataStream.partitionCustom enables an important use case. What I have in mind is performing partitioned enrichment, where each instance can preload a slice of a static dataset that is being used for enrichment. For an example,

[jira] [Created] (FLINK-18706) Stop with savepoint cannot guarantee exactly-once for kafka source

Yumeng Zhang created FLINK-18706: Summary: Stop with savepoint cannot guarantee exactly-once for kafka source Key: FLINK-18706 URL: https://issues.apache.org/jira/browse/FLINK-18706 Project: Flink

[jira] [Created] (FLINK-18705) Debezium-JSON throws NPE when tombstone message is received

Jark Wu created FLINK-18705: --- Summary: Debezium-JSON throws NPE when tombstone message is received Key: FLINK-18705 URL: https://issues.apache.org/jira/browse/FLINK-18705 Project: Flink Issue

[VOTE] FLIP-129: Refactor Descriptor API to register connector in Table API

Hi all, I would like to start the vote for FLIP-129 [1], which is discussed and reached consensus in the discussion thread [2]. The vote will be open until 27th July (72h), unless there is an objection or not enough votes. Best, Jark [1]:

[jira] [Created] (FLINK-18704) Support DECIMAL types in datagen Table source connector

Fabian Hueske created FLINK-18704: - Summary: Support DECIMAL types in datagen Table source connector Key: FLINK-18704 URL: https://issues.apache.org/jira/browse/FLINK-18704 Project: Flink

Re: [DISCUSS] FLIP-130: Support for Python DataStream API (Stateless Part)

Hi Aljoscha, Thank you for your response. I'll keep these two helper methods in the Python DataStream implementation. And thank you all for joining in the discussion. It seems that we have reached a consensus. I will start a vote for this FLIP later today. Best, Shuiqiang Hequn Cheng

[jira] [Created] (FLINK-18703) Use new data structure converters when legacy types are not present

Timo Walther created FLINK-18703: Summary: Use new data structure converters when legacy types are not present Key: FLINK-18703 URL: https://issues.apache.org/jira/browse/FLINK-18703 Project: Flink

Re: [DISCUSS] FLIP-130: Support for Python DataStream API (Stateless Part)

Thanks a lot for your valuable feedback and suggestions! @Aljoscha Krettek +1 to the vote. Best, Hequn On Fri, Jul 24, 2020 at 5:16 PM Aljoscha Krettek wrote: > Thanks for updating! And yes, I think it's ok to include the few helper > methods such as "readFromFile" and "print". > > I think we

[jira] [Created] (FLINK-18702) Flink elasticsearch connector leaks threads and classloaders thereof

Jun Qin created FLINK-18702: --- Summary: Flink elasticsearch connector leaks threads and classloaders thereof Key: FLINK-18702 URL: https://issues.apache.org/jira/browse/FLINK-18702 Project: Flink

Re: [DISCUSS] FLIP-129: Refactor Descriptor API to register connector in Table API

I'm jumping in quite late but I think overall this is a very good effort and it's in very good shape now. Best, Aljoscha On 24.07.20 10:24, Jark Wu wrote: Thanks Dawid, Regarding (3), I think you mentioned it will affect other behavior, e.g. listing tables, is a strong reason. I will at

Re: [DISCUSS] FLIP-130: Support for Python DataStream API (Stateless Part)

Thanks for updating! And yes, I think it's ok to include the few helper methods such as "readFromFile" and "print". I think we can now proceed to a vote! Nice work, overall! Best, Aljoscha On 16.07.20 17:16, Hequn Cheng wrote: Hi, Thanks a lot for your discussions. I think Aljoscha makes

Re: Inconsistent behavior between different states with ListState.get().iterator().remove()

That is a very good observation! In an ideal world, I would say we disallow #remove() because we cannot efficiently implement it for RocksDB and we should keep the behaviour consistent between the backends. Now that we already have the functionality for the heap-based backends I think we

[jira] [Created] (FLINK-18701) NOT NULL constraint is not guaranteed when aggregation split is enabled

Jark Wu created FLINK-18701: --- Summary: NOT NULL constraint is not guaranteed when aggregation split is enabled Key: FLINK-18701 URL: https://issues.apache.org/jira/browse/FLINK-18701 Project: Flink

Re: [DISCUSS] FLIP-129: Refactor Descriptor API to register connector in Table API

Thanks Dawid, Regarding (3), I think you mentioned it will affect other behavior, e.g. listing tables, is a strong reason. I will at least consider implementing it in the `TableSourceQueryOperation` way to avoid affecting other behaviors. I have updated the FLIP. Anyway, this is implementation

[jira] [Created] (FLINK-18700) Debezium-json format throws Exception when PG table's IDENTITY config is not FULL

Leonard Xu created FLINK-18700: -- Summary: Debezium-json format throws Exception when PG table's IDENTITY config is not FULL Key: FLINK-18700 URL: https://issues.apache.org/jira/browse/FLINK-18700

Re: [DISCUSS] FLIP-129: Refactor Descriptor API to register connector in Table API

Thanks Jark for the update. The latest FLIP looks well. I like Dawid’s proposal of TableDescriptor. Best Leonard Xu > 在 2020年7月23日，22:56，Jark Wu 写道： > > Hi Timo, > > That's a good point I missed in the design. I have updated the FLIP and added > a note under the `KafkaConnector` to mention

Re: [DISCUSS] FLIP-129: Refactor Descriptor API to register connector in Table API

Thanks for the update. The FLIP looks good, I think it is time to vote. Best, Jingsong On Fri, Jul 24, 2020 at 3:21 PM Dawid Wysakowicz wrote: > Hi Jark, > > Ad. 1 > > Personally I don't see any benefit of having the specific descriptors > (KafkaDescriptor/ElasticDescriptor/...). E.g. the

Re: [DISCUSS] FLIP-129: Refactor Descriptor API to register connector in Table API

Hi Jark, Ad. 1 Personally I don't see any benefit of having the specific descriptors (KafkaDescriptor/ElasticDescriptor/...). E.g. the KafkaDescriptor would not differ at all from other descriptors. I don't think returning always a TableDescriptor would be confusing for users. Therefore I am

[jira] [Created] (FLINK-18699) Allow variables for column names in Scala Table API

Timo Walther created FLINK-18699: Summary: Allow variables for column names in Scala Table API Key: FLINK-18699 URL: https://issues.apache.org/jira/browse/FLINK-18699 Project: Flink Issue