Details
-
Bug
-
Status: Patch Available
-
Normal
-
Resolution: Unresolved
-
None
-
Degradation - Resource Management
-
Normal
-
Normal
-
User Report
-
All
-
None
-
Description
In the `ModificationStatement` class, the `casInternal` method opens a row iterator without closing it, causing the iterator to leak resources. Here is a link to the relevant code in the `trunk` branch.
It seems that `cassandra-3.0.30` has the bug, but `cassandra-2.2.19` does not have it. Is it correct to target `cassandra-3.0.30`?
What is the best practice for testing this kind of bug fix? It seems like a low complexity fix. This is my first contribution to the Cassandra community, so any guidance is appreciated. Thanks!