Looks like there were issues with the native parts. Mike McCandless
notes this in [1]. If we reuse the Lucene code, I think it'll work
for Cassandra.
1. https://issues.apache.org/jira/browse/LUCENE-2500
On Tue, Aug 2, 2011 at 9:42 PM, Jonathan Ellis wrote:
> Tried and failed. https://issues.ap
Tried and failed. https://issues.apache.org/jira/browse/CASSANDRA-1902
On Tue, Aug 2, 2011 at 11:24 PM, Jason Rutherglen
wrote:
> Cassandra 'compacts' the way Lucene 'merges' segments. One
> interesting new feature built into Lucene is [1] which avoids loading
> the source files into the system
Cassandra 'compacts' the way Lucene 'merges' segments. One
interesting new feature built into Lucene is [1] which avoids loading
the source files into the system IO cache on compaction / merge.
Perhaps Cassandra already has this feature?
1.
https://builds.apache.org/job/Lucene-trunk/javadoc/all
Please test removetoken thoroughly for this release,
https://issues.apache.org/jira/browse/CASSANDRA-2496 was a significant
change that completely reworked the existing (broken) behavior.
-Brandon
On Tue, Aug 2, 2011 at 1:28 PM, Sylvain Lebresne wrote:
> We have found and fixed (CASSANDRA-2829)
We have found and fixed (CASSANDRA-2829) a regression of 0.8, due to
CASSANDRA-2419, causing commit log segments to be potentially deleted while
still dirty. There has been a number of other important bug fixes since 0.8.2,
including the fix of "remove token".
I thus propose the following artifact
