Open FarhadJabiyev opened 3 weeks ago
Likely caused by #310
Likely caused by #310
Hey, great finding and thanks for bringing those two issues together. I actually tried updating to the latest Event Hubs SDK locally, but I encountered more changes than I anticipated. The Event Hubs team has split some class definitions into multiple ones for better separation of concerns (SoC), which made the process more complex than expected. That's when I decided to give up and created the issue. :) Seems the issue #310 has even PR.
Thanks all - yes I think this is probably caused by not using the latest EH SDK. There's an active effort to do that (https://github.com/microsoft/durabletask-netherite/pull/385) but it's lagging behind due to other urgent work we're tackling for reliability, though having the latest EH SDK would also help in general.
@FarhadJabiyev - since this likely caused by the old EH SDK, do you mind if we close this in favor of centralizing the discussion here: https://github.com/microsoft/durabletask-netherite/issues/310?
@davidmrdavid Yes, totally.
Description I am encountering an issue when using the new Azure Event Hubs Emulator with Netherite. The emulator connection string includes an additional parameter: UseDevelopmentEmulator=true. However, due to outdated Event Hubs packages in Netherite (some of which are now deprecated), this parameter causes the following exception:
Background The UseDevelopmentEmulator parameter is used to specify that the Event Hubs connection is targeting the development emulator rather than a live service. However, since Netherite relies on outdated versions of the Event Hubs SDK, it does not recognize this parameter, resulting in the exception described above.
Impact Currently, the only workaround is to set up a real Event Hub service for development purposes, which is not ideal. This is because:
Request Could you please update Netherite to support the latest Event Hubs SDK or provide a workaround for handling the UseDevelopmentEmulator parameter in connection strings? This would help streamline our development process and reduce the need for a full Event Hub service in development.