Thanks @Qingsheng and @Leonard. Let's work together to improve the quality
of different connectors.
Regards.
On Fri, Oct 29, 2021 at 2:39 PM Qingsheng Ren wrote:
> Hi Ken,
>
> Thanks for reaching out and sorry for making confusion!
>
> Like Leonard mentioned we definitely honor every
Hi Ken,
Thanks for reaching out and sorry for making confusion!
Like Leonard mentioned we definitely honor every connector in Flink community.
And under the situation that we have more and more connectors to maintain and
limited guys and resources focusing on connector-wise issues, some
Hi, Peng
There’s no doubt that RabbitMQ is a good open source community with active
users.
I understand what @renqschn means is that Flink RabbitMQ Connector is one
connector with few users among the many connectors in the Flink project. From
my observation, the connector that is used more
I am one of the Forum Moderators for RabbitMQ, which does have a lot of
active users. :)
If you have any questions about RMQ please subscribe to its official group
and ask there.
rabbitmq-users+subscr...@googlegroups.com
Regards.
On Fri, Oct 29, 2021 at 11:09 AM 任庆盛 wrote:
> 您好，
>
> 从代码来看
您好，
从代码来看 RabbitMQ Sink 的确没有语义保证。目前 RabbitMQ
由于社区用户不多，相对的维护频率也比较低，如果感兴趣的话也欢迎您参与社区的贡献～
> 2021年10月28日 下午7:53，wx liao 写道：
>
> 你好：
>
> 冒昧打扰，最近项目在使用flink,sink端是rabbitmq,但是查看项目源码发现RMQSink好像并没有对消息不丢失做保证，没有看到有使用waitForConfirm()或者是confirm
> listener,想问一下RMQSink部分是否没有保证at least
你好：
冒昧打扰，最近项目在使用flink,sink端是rabbitmq,但是查看项目源码发现RMQSink好像并没有对消息不丢失做保证，没有看到有使用waitForConfirm()或者是confirm
listener,想问一下RMQSink部分是否没有保证at least once?希望可以得到解答，谢谢。
> 在 2021年10月28日，下午7:53，wx liao 写道：
>
> 你好：
>
> 冒昧打扰，最近项目在使用flink,sink端是rabbitmq,但是查看项目源码发现RMQSink好像并没有对消息不丢失做保证，没有看到有使用waitForConfirm()或者是confirm
> listener,想问一下RMQSink部分是否没有保证at least once?希望可以得到解答，谢谢。
