Need the ability to define a IoT Hub Device Connection String per writer group. #2426
Description
Is your feature request related to a problem? Please describe.
In a scenario of having one IoT Hub and one single IoT Edge with high data throughput (50.000+ OPC UA nodes) it is currently not possible to efficiently use multiple IoT Hub partitions (since usage of an IoT Hub partition is bound to a hash of the DeviceID, and there's only a single DeviceID in this scenario). In this case, only one IoT Hub partition will be used to process the data, and altering the partitioning scheme in the IoT Hub is not possible.
Describe the solution you'd like
The ability to define a IoT Hub Device Connection String per writer group.
Describe alternatives you've considered
Distributing the OPC UA node configuration over multiple IoT Edge devices, so that each IoT Edge device will be assigned a partition in the IoT Hub, which is expensive and not always practical or even needed.
Additional context
It is ok if connection strings are stored in the published nodes configuration file.