Allow control of which partition in MessageHub the IoT Platform Historical Data Storage Extension publishes to
Current: The publishing to MessageHub has device level affinity to MessageHub topics. i.e. *all* events for a given device will go to the same partition in the MessageHub topic.
Which partition device events are published to is then based on the result of hashing . In effect this means, depending on the device type Ids and the device instance Ids, we may legitimately publish all of the events to the same partition in the topic.
Problem with this: For the current scope of work, the assignment of messages to the partition is not topic of concern for me. But thinking about the scenario where the load would be required to be distributed across multiple partitions for multiple consumers to catch up with the messages when the high volume of events are published to the topic
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions