few mqtt topics inbound connector(s?)

[pistoletov1974]

How to get data from multiple mqtt topics correctly - by running multiple connectors with their own configurations? Or am I describing several mqtt incoming topics in one configuration? I try first one

cdk  deploy  start --config sql_tele.yaml --ipkg infinyon-sql-sink-0.3.3.ipkg
cdk  deploy  start --config tele_emqx.yaml --ipkg infinyon-mqtt-source-0.2.5.ipk

and receive error:
... checking package
Error: Failed to deploy from ipkg file

Caused by:
Text file busy (os error 26)

[drc-infinyon]

@pistoletov1974 Are these for different sources of data?

@digikata - is this one example of what you referenced yesterday?

[pistoletov1974]

@drc-infinyon yes, different topics from the same mqtt broker
I suppouse my situation described in this issue

[digikata]

That is correct, we have a PR that is being reviewed for merge that addresses this issue, should be coming up soon

[ajhunyady]

This issue has been resolved.

[sehz]

There is a limitation now with connector. Can only start a single configuration in same directory. Workaround is to create separate directory for each configuration

[ajhunyady]

@digikata, let's deploy the fix so @pistoletov1974 can confirm it works.

[ajhunyady]

@pistoletov1974 can you please check if the fix works?

[pistoletov1974]

@ajhunyady i need to update connectors only or full fluvio ?
Can you give me few tips about this issue. issue with connectror build I am not specialist in RUST. How can i build this connector? I suppouse problem is with name of package.

[ajhunyady]

@pistoletov1974, the fix was in CDK. So, all you need to do is fvm install latest (fvm -> fluvio version manager). This command will download the latest binaries, such as fluvio and cdk and switch your environment to use them.

Once you are done testing, you can switch back to the stable by using fvm switch stable.

To check what versions you are running use fvm list.

[pistoletov1974]

@digikata @ajhunyady I launched successfully few connectors from same directory-)

[ajhunyady]

Thank you for checking @pistoletov1974! The fix will be added to the next stable release targeted for next week.