[
https://issues.apache.org/jira/browse/FLINK-32673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831873#comment-17831873
]
Claire McCarthy edited comment on FLINK-32673 at 3/28/24 4:12 PM:
------------------------------------------------------------------
Hey all! What's the status on this PR:
[https://github.com/apache/flink-connector-gcp-pubsub/pull/2
|https://github.com/apache/flink-connector-gcp-pubsub/pull/2]?
I have a new implementation of the Google Pub/Sub source connector that is
almost ready. The goal of the new implementation is three-fold:
# Implement
[FLIP-27|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95653748]
# Address some users' performance concerns
## change the implementation from using Pu/Sub Pull API to Pub/Sub Streaming
Pull API
## implement automatic message leasing
# Re-engage with this connector and start actively supporting it
I'm wondering how best to proceed considering the status of the currently
outstanding PR. To me, there appears to be two options:
# Get the outstanding PR merged in and then open a PR with the new
implementation (which might overwrite a significant amount of what was just
merged in)
# We close the outstanding pull request and I open a fresh pull request with
the new implementation
Let me know your thoughts; thanks!
was (Author: JIRAUSER304788):
Hey all! What's the status on this
[PR|[https://github.com/apache/flink-connector-gcp-pubsub/pull/2]]?
I have a new implementation of the Google Pub/Sub source connector that is
almost ready. The goal of the new implementation is three-fold:
# Implement
[FLIP-27|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95653748]
# Address some users' performance concerns
## change the implementation from using Pu/Sub Pull API to Pub/Sub Streaming
Pull API
## implement automatic message leasing
# Re-engage with this connector and start actively supporting it
I'm wondering how best to proceed considering the status of the currently
outstanding PR. To me, there appears to be two options:
# Get the outstanding PR merged in and then open a PR with the new
implementation (which might overwrite a significant amount of what was just
merged in)
# We close the outstanding pull request and I open a fresh pull request with
the new implementation
Let me know your thoughts; thanks!
> Migrage Google PubSub connector to V2
> -------------------------------------
>
> Key: FLINK-32673
> URL: https://issues.apache.org/jira/browse/FLINK-32673
> Project: Flink
> Issue Type: Sub-task
> Reporter: Alexander Fedulov
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
