Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
STORM-2912 Revert optimization of sharing tick tuple (1.x) #2532
More detail: https://issues.apache.org/jira/browse/STORM-2912
We must cherry-pick this into 1.1.x-branch and 1.0.x-branch as well, and I guess it will be no conflict.
Will also craft a patch for master branch shortly.
It is really hard to think such side effect while applying optimization like this. It is fairly easy to think that tuple is immutable, and it is true for interface
Due to how acker works, we allow updating XOR value to
It would be better if we have some way to address without incurring performance hit.