Feat: Add Context Cancelation

[audipasuatmadi]

Problem

Currently the micro-batch does not care about context-cancellation. This could be an issue in case user cancels a request such as when user ends an operation mid-flight.

Expected Behavior

When context cancellation is made, the buffer is reset and nothing can be flushed. The expected behavior is open for discussion.

[doug-benn]

Hello,

This interests me, the whole buffer would be reset, What if a different context is used on subsequent adds?

Should the context of that add be stored and then the context be "checked" when the data in read?

What about other ways of removing items from the buffer?

Sorry seems like just more question not really answers

Thanks
--Doug

[audipasuatmadi]

Hi @doug-benn,

Thank you very much for your interest in the open-source project.
That's a good question, and yeah I think that'll be an edge-case. We have an open pull-request overhauling the overall architecture, thus the approach to context cancellation might differ; #5

Do you have suggestion for the approach once the pull-request above merged?

-- Audi

[doug-benn]

Hello,

It looks like after the overhaul PR the buffer would have a context that could be cancelled if a added items context was cancelled, reseting the buffer.

I'm not sure on the use case of cancelling the context. e.g. IoT device won't cancel an update to a value? What role does the context on a item being added play?

Again sorry for just questions 😄

-- Doug

[audipasuatmadi]

Hi @doug-benn,

Sorry for the late response, got busy at work.
Actually that's a very interesting perspective, thank you!
Perhaps I was thinking of something that doesn't have a real use-case (yet). Maybe we can YAGNI for now and focus on the things that matters.

Please feel free to join the Pull-Request review, your insight will be very valuable for us all.

Thanks, Audi.

[audipasuatmadi]

In case we found a real use-case of the context cancellation, perhaps we can have an open-discussion to define the expected behaviors.