Documentation mentions using AggregationManager, which does not exist
Closed this issue · 4 comments
The existing README.md for the python package and the potential_data_loss.md both mention using the AggregationManager from version 1.2.0 onwards. However, this class does not exist in the mentioned versions in the python code at all.
Correct - this documentation was incorrect and has been deleted.
Has the underlying issue with the KCL dropping messages not destined for the assigned consumer been fixed? If not, then I think the documentation should have been modified, rather than deleted entirely. It's still linked from the front README with an all caps DATA LOSS CAN OCCUR. This is now a dead link.
It would be very helpful to still have an explanation of the underlying issue, even if there is no workaround.
Documentation has been restored and corrected.