[
https://issues.apache.org/jira/browse/CASSANDRA-19624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19624:
-----------------------------------------
Bug Category: Parent values: Degradation(12984)Level 1 values: Resource
Management(12995)
Complexity: Normal
Component/s: Legacy/Core
Discovered By: User Report
Fix Version/s: 4.0.x
4.1.x
5.0.x
5.x
Severity: Normal
Status: Open (was: Triage Needed)
> ModificationStatement#casInternal leaks RowIterator
> ---------------------------------------------------
>
> Key: CASSANDRA-19624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19624
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Michael Marshall
> Assignee: Michael Marshall
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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.
> [https://github.com/apache/cassandra/blob/a77a2d10b1d247ed920b75df79f982a3b7c6a431/src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java#L680-L684]
>
> 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!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
