You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@streampipes.apache.org by "Dominik Riemer (Jira)" <ji...@apache.org> on 2022/11/26 15:29:00 UTC

[jira] [Commented] (STREAMPIPES-625) Refactor the Pulsar Protocol Adapter

    [ https://issues.apache.org/jira/browse/STREAMPIPES-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17639451#comment-17639451 ] 

Dominik Riemer commented on STREAMPIPES-625:
--------------------------------------------

This issue has been migrated to https://github.com/apache/streampipes/issues/737

> Refactor the Pulsar Protocol Adapter
> ------------------------------------
>
>                 Key: STREAMPIPES-625
>                 URL: https://issues.apache.org/jira/browse/STREAMPIPES-625
>             Project: StreamPipes
>          Issue Type: Improvement
>          Components: Connect
>            Reporter: Zike Yang
>            Assignee: Zike Yang
>            Priority: Normal
>              Labels: pull-request-available
>             Fix For: 0.90.0
>
>
> * {*}Implement SupportsRuntimeConfig{*}: Currenty, the pulsar adapter still implements the deprecated interface `ResolvesContainerProvidedOptions`. Need to implement SupportsRuntimeConfig.
>  * *Add new setting `pulsar-subscription-name`:* Currently, the pulsar consumer uses the random subscription name, this can not ensure the data consistent for the users
>  * {*}Refactor the adapter by using the asynchronous programming model{*}. Avoid using raw thread to handle the consumption.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)