The use case is to support an unbounded stream-stream join, where the
elements are arriving in roughly time sorted order. Removing a specific
element from the timestamp indexed collection is necessary when a match is
found. Having clearRange is helpful to expire elements that are no longer
relevant
Hi Ismaël
Thank you for the review and merge. We hope to keep improving the Twister2
runner as the frameworks develops as well. I will also try to help out more
within the community since i gained a bit of experience with the runners
developing this one.
Best Regards,
Pulasthi
On Tue, Sep 15, 20
Thanks Ismael and Robert for your thoughts on this.
I’m going to check the parity and see if we need to do any changes on this.
PS: Sorry, I screwed up the subject of this thread (“v2" instead of "v1"), it
definitively has to be “Deprecation of AWS SDK v1 IO connectors” (thanks to
Ismael for po
