Adding Chandradeep to CC, in case he didn't subscribe to the list.

On Tue, 9 May 2023 at 18:31, Nandor Soma Abonyi
<nsabo...@icloud.com.invalid> wrote:
>
> Dear Chandradeep,
>
> Though I haven't seen your configuration yet, I tried to test the scenario. 
> If you want to listen to different topics with a single processor, you need 
> to use wildcards. If you have two clients that are publishing to 
> buildings/A/1/temperature and buildings/A/2/temperature, then the subscriber 
> client’s topic filter should be buildings/A/+/temperature. With the latest 
> version (1.21.0) this works as expected. I’ve also tested the “workaround” 
> approach to create two consumers but it also worked correctly. I advise you 
> to revise your configuration. If you need additional help, please share it on 
> the user's mailing list or through the NiFi Slack channel.
>
> Best regards,
> Nandor Soma Abonyi
>
> > On May 6, 2023, at 2:28 PM, Nandor Soma Abonyi 
> > <nsabo...@icloud.com.INVALID> wrote:
> >
> > Dear Chandradeep,
> >
> > It seems like the images didn’t go through.
> > Could you attach them again?
> >
> > Best regards,
> > Nandor Soma Abonyi
> >
> >> On 2023. May 6., at 13:59, Chandradeep Kumar 
> >> <chandradeep.ku...@india.nec.com> wrote:
> >>
> >> 
> >> Dear Dev,
> >>
> >> I’m trying to handle a scenario where more than one topic could be able to 
> >> subscribe to a MQTT Broker via ConsumeMQTT processor.
> >>
> >> Currently I’m able to subscribe single topic and receive message which is 
> >> published on same topic.
> >>
> >> Below configuration of ConsumeMQTT works fine:
> >>
> >>
> >> But when I configured more than one topic in this processor then it is not 
> >> working:
> >>
> >>
> >>
> >> When I tried to create two consumeMQTT processor which are connected with 
> >> single funnel then both are not working. However when I stopped anyone 
> >> then its started working.
> >>
> >> Request you to kindly help me out on this use case.
> >> Thanks in advance.
> >>
> >> Regards,
> >> Chandradeep
> >> The contents of this e-mail and any attachment(s) are confidential and 
> >> intended for the named recipient(s) only. It shall not attach any 
> >> liability on the originator or NEC Corporation India Private Limited or 
> >> its affiliates. Any views or opinions presented in this email are solely 
> >> those of the author and may not necessarily reflect the opinions of NEC 
> >> Corporation India Private Limited or its affiliates. Any form of 
> >> reproduction, dissemination, copying, disclosure, modification, 
> >> distribution and / or publication of this message without the prior 
> >> written consent of the author of this e-mail is strictly prohibited. If 
> >> you have received this email in error please delete it and notify the 
> >> sender immediately.
>

Reply via email to