[
https://issues.apache.org/jira/browse/CASSANDRA-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094704#comment-13094704
]
Hudson commented on CASSANDRA-3107:
-----------------------------------
Integrated in Cassandra #1061 (See
[https://builds.apache.org/job/Cassandra/1061/])
add CompactionInfo.id field
patch by Stu Hood; reviewed by jbellis for CASSANDRA-3107
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1163691
Files :
* /cassandra/trunk/src/java/org/apache/cassandra/cache/AutoSavingCache.java
*
/cassandra/trunk/src/java/org/apache/cassandra/db/compaction/CompactionInfo.java
*
/cassandra/trunk/src/java/org/apache/cassandra/db/compaction/CompactionIterable.java
*
/cassandra/trunk/src/java/org/apache/cassandra/db/compaction/CompactionManager.java
*
/cassandra/trunk/src/java/org/apache/cassandra/db/index/SecondaryIndexBuilder.java
> CompactionInfo id is not stable
> -------------------------------
>
> Key: CASSANDRA-3107
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3107
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-Stable-id-for-CompactionInfo.txt
>
>
> The original intention of displaying the hashcode of the CompactionInfo for a
> compaction was that it would be stable and unique for the lifetime of the
> compaction. But at some point in the refactoring, we moved to
> new-object-per-call, which means that the hashcode is not stable.
> Giving the CompactionInfo object an id field that can be generated from the
> hashcode of the actual compaction task would solve this problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
