Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2532
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 `Tuple`, but no longer true for `TupleImpl`. Ideally `TupleImpl`
should be also immutable.
Due to how acker works, we allow updating XOR value to `TupleImpl`, and due
to how we measure metrics, we allow setting timestamp to `TupleImpl`.
It would be better if we have some way to address without incurring
performance hit.
---
