[
https://issues.apache.org/jira/browse/CASSANDRA-19624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844683#comment-17844683
]
Michael Marshall commented on CASSANDRA-19624:
----------------------------------------------
The bug is as early as 3.0, but I am targeting 4.0. Please let me know if we
should change that.
> ModificationStatement#casInternal leaks RowIterator
> ---------------------------------------------------
>
> Key: CASSANDRA-19624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19624
> Project: Cassandra
> Issue Type: Bug
> Reporter: Michael Marshall
> Assignee: Michael Marshall
> Priority: Normal
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
