Re: [DISCUSS] FLIP-72: Introduce Pulsar Connector

gt; merge in the next couple weeks. > > Thanks, > Bowen > > > On Mon, Dec 23, 2019 at 7:03 PM Yijie Shen > wrote: > > > Hi Bowen, > > > > I've done updated the design doc, PTAL. > > Btw the PR for catalog is https://github.com/apache/flink/pull

[jira] [Created] (FLINK-15624) Pulsar Sink

Yijie Shen created FLINK-15624: -- Summary: Pulsar Sink Key: FLINK-15624 URL: https://issues.apache.org/jira/browse/FLINK-15624 Project: Flink Issue Type: Sub-task Reporter: Yijie

Re: [DISCUSS] FLIP-72: Introduce Pulsar Connector

hings out of this FLIP and will address them in > separate > >> > FLIPs. Including: > >> > 1. Per split event time. > >> > 2. Event time alignment. > >> > 3. Fine grained failover for SplitEnumerator failure. > >> > > >&g

[jira] [Created] (FLINK-15089) Pulsar Catalog

Yijie Shen created FLINK-15089: -- Summary: Pulsar Catalog Key: FLINK-15089 URL: https://issues.apache.org/jira/browse/FLINK-15089 Project: Flink Issue Type: Sub-task Components

Re: [DISCUSS] FLIP-72: Introduce Pulsar Connector

Yijie Shen wrote: > Hi everyone, > > Glad to receive your valuable feedbacks. > > I'd first separate the Pulsar catalog as another doc and show more design > and implementation details there. > > For the current FLIP-72, I would separate it into the sink part for > curre

Re: [DISCUSS] FLIP-72: Introduce Pulsar Connector

ock the contribution for sink (or source) > > and keep the discussion more focus. > > I also left some comments in the documentation. > > > > Thanks, > > Jark > > > > On Thu, 17 Oct 2019 at 11:24, Yijie Shen > > wrote: > > > > > H

Re: [DISCUSS] FLIP-72: Introduce Pulsar Connector

mapping a pulsar cluster and > 'tenant/namespace' respectively to Flink's 'catalog' and 'database'. I > wonder whether it totally makes sense, or should we actually map > "tenant" > to "catalog", and "namespace" to "database"? >

[jira] [Created] (FLINK-14146) Introduce Pulsar connector

Yijie Shen created FLINK-14146: -- Summary: Introduce Pulsar connector Key: FLINK-14146 URL: https://issues.apache.org/jira/browse/FLINK-14146 Project: Flink Issue Type: New Feature

[DISCUSS] FLIP-72: Introduce Pulsar Connector

Hi everyone, Per discussion in the previous thread , I have created FLIP-72 to kick off a more detailed discussion on the Flink Pulsar connector:

Re: [DISCUSS] Contribute Pulsar Flink connector back to Flink

Hi Fabian, It's yijieshen Thanks for your help! On Thu, Sep 19, 2019 at 4:52 PM Fabian Hueske wrote: > > Hi Yijie, > > I can give you permission if you tell me your Confluence user name. > > Thanks, Fabian > > Am Do., 19. Sept. 2019 um 10:49 Uhr schrieb Yij

Re: [DISCUSS] Contribute Pulsar Flink connector back to Flink

; > > > > > but we may still have to maintain two code bases. For the > > > > existing > > > > > > > > > connectors, we have to do that anyways. But it would be good > > to > > > > > avoid > > > > > > > > > intro

Re: [DISCUSS] Contribute Pulsar Flink connector back to Flink

ffered some help already, I can also help a bit. I hope that > > > > > between us, we can cover this. > > > > > > > > > > ## Contribute now, or wait for FLIP-27 > > > > > > > > > > As Becket said, FLIP-27 is actually making some

Re: [DISCUSS] Contribute Pulsar Flink connector back to Flink

, 2019 at 8:56 AM Becket Qin > > > wrote: > > > > > > > > > > > Hi Sijie and Yijie, > > > > > > > > > > > > Thanks for sharing your thoughts. > > > > > > > > > > > > Jus

Re: [DISCUSS] Contribute Pulsar Flink connector back to Flink

; >> We believe Pulsar is not just a simple data sink or source for Flink. > > It > > > >> actually can be a fully integrated streaming data storage for Flink in > > > many > > > >> areas (sink, source, schema/catalog and state). The combination of > >

[DISCUSS] Contribute Pulsar Flink connector back to Flink

://cwiki.apache.org/confluence/display/FLINK/FLIP-37%3A+Rework+of+the+Table+API+Type+System [4] https://cwiki.apache.org/confluence/display/FLINK/FLIP-30%3A+Unified+Catalog+APIs Best, Yijie Shen

[jira] [Created] (FLINK-3976) Alias fields of physical plan node to avoid name collision with Calcite protected fields

Yijie Shen created FLINK-3976: - Summary: Alias fields of physical plan node to avoid name collision with Calcite protected fields Key: FLINK-3976 URL: https://issues.apache.org/jira/browse/FLINK-3976

Re: Preparing Table API & SQL for Flink 1.1.0

Hi Fabian, The priority seems reasonable to me. I skimmed through your TPCH branch and find data type and related functions would be quite important to enable most of TPC-H queries. I would try out your TPC-H branch and pick up some issues you filed these two days for the 1.1.0 release. Hope

[jira] [Created] (FLINK-3754) Add a validation phase before construct RelNode using TableAPI

Yijie Shen created FLINK-3754: - Summary: Add a validation phase before construct RelNode using TableAPI Key: FLINK-3754 URL: https://issues.apache.org/jira/browse/FLINK-3754 Project: Flink

[jira] [Created] (FLINK-3736) Move toRexNode and toAggCall logic into Expressions

Yijie Shen created FLINK-3736: - Summary: Move toRexNode and toAggCall logic into Expressions Key: FLINK-3736 URL: https://issues.apache.org/jira/browse/FLINK-3736 Project: Flink Issue Type

[jira] [Created] (FLINK-3723) Aggregate Functions and scalar expressions shouldn't be mixed in select

Yijie Shen created FLINK-3723: - Summary: Aggregate Functions and scalar expressions shouldn't be mixed in select Key: FLINK-3723 URL: https://issues.apache.org/jira/browse/FLINK-3723 Project: Flink