chore: introduce the Operation trait to enforce consistency between operations #2435
Conversation
Currently this is nothing but a shim that ensures everything implements IntoFuture, which they all already do, but in the future this will help enforce consistency as well as provide common behaviors.
|
I agree we should start enforcing operations to have a consistent trait interface. For future enhancement on trait method I'd like to see is the ability to obtain the commit data before it's actually committed. This would allow an escape hatch for advanced users to escape our commit process. |
|
To David's point this is why I think a marker trait by itself it maybe not sufficient, we should eventually move towards a trait that implements and expected life cycle of an operation (or multiple smaller ones that implement a part of it) the most ready example I can think of is something similar to Hadoop's commit protocol, but we should do something that makes sense for us, I'm just using as an example of generalization of such a process. |
|
@hntd187 that's certainly the plan here 😄 I just wanted to get something started we could begin hanging functionality off of |
I am spinning this pull request out from some of my other in-flight work to extend behaviors with the operations.
The motivation here is to provide a base trait which can act as a standards-bearer for the operations implementations. Right now this is only enforcing
IntoFuturebut there are a couple of other changes I am actively working on which I hope will dramatically clean up these operations and enable some of the use-cases that @hntd187 and I have been exploring.