Repository navigation
Correlation Vector 3.0 Support #7
Description
Hi, excuse my ignorance, I'm still trying to familiarize myself with vector clocks and tracing through distributed systems.
Reading through the cV 3.0 spec suggests that there should be an implicit reset operation when performing increment, spin, or extend which truncates the vector clock and spits out a suffix S and a replacement M that should be recorded to allow for reconstructing the trace later.
I can't seem to find this functionality in this implementation. I'm guessing this is because it implements cV 2.1 not 3.0. Is this correct?
If so, is there a timeline for 3.0 spec support?
I'm tempted to attempt extending this implementation myself, but still need to do more research as I'm unsure how much of an undertaking that would be. Any further advice/warnings/cautions with respect to this would be greatly appreciated.
Activity
lemejia commentedon May 16, 2019
You are correct, the version implemented is 2.1.
There is some work left before getting a timeline for 3.0 once the document is finally approved. I'll work on getting more clarity on that and I'll provide you an update as soon as I find more information.
If you want to work on creating an implementation for cV 3.0 using the current draft, please feel free to do so. We are more than happy accepting collaborations. But, as a reminder, the doc is still in review and may change in its final form.