| clear query|facets|time |
Search criteria: TieredMergePolicy.
Results from 51 to 60 from
178 (0.428s).
|
|
|
Loading phrases to help you
refine your search...
|
|
[LUCENE-4164] Improve IndexWriter.addIndexes(IndexReader) javadocs - Lucene - [issue]
|
|
..., and not e.g. like MergePolicy does at mergeFactor steps. Therefore I think it'd be good to clarify it to the user, and also encourage him to call this method several times if he has many Index...
|
|
...IndexWriter.addIndexes(IndexReader) needs some improvements:
It falsely states that this method blocks any add/delete documents attempts.
It merges all input IndexReaders at once...
|
[+ show more]
[- hide]
| ...Readers to merge.
And while at it, mentioning that the IR can be opened with termIndexInterval=-1 since we don't need it during merge will be good – saves RAM.
I'll attach a patch shortly.... |
|
|
http://issues.apache.org/jira/browse/LUCENE-4164
Author: Shai Erera,
2012-06-26, 08:31
|
|
|
ConcurrentMergeScheduler may spawn MergeThreads forever - Lucene - [mail # dev]
|
|
...Hi I think I've hit a bug in ConcurrentMergeScheduler, but I'd like those who are more familiar with the code to review it. I ran TestStressSort.testSort() and started to get AIOOB...
|
|
... exceptions from MergeThread, the CPU spiked to 98-100% and did not end for a couple of minutes, until I was able to regain control and kill the process (looks like an infinite loop). To reproduce...
|
[+ show more]
[- hide]
| ... to reproduce it with a JUnit test or something so that it will happen consistently. When I debugged-trace the test, I noticed that MergeThread are just spawned forever. The reason is this: In CMS.merge... |
| ...(IndexWriter) there's a 'while (true)' loop which does 'while (mergeThreadCount() >= maxThreadCount)' and if false just spawns a new MergeThread. On the other hand, in MergeThread.run there's a try... |
| ... itself from the queue and CMS will spawn a new thread. That puts the code into an infinite loop. That sounds like a bug to me ... I think that if MergeThread hits any exception, the merge should... |
|
|
Author: Shai Erera,
2009-04-28, 10:09
|
|
|
Enhance SnapshotDeletionPolicy to allow taking multiple snapshots - Lucene - [mail # dev]
|
|
...Hi Today, SnapshotDeletionPolicy (SDP) allows taking only one snapshot. I need to be able to take multiple snapshots. Consider multiple processes doing several things on the index - each...
|
|
|
Author: Shai Erera,
2010-04-27, 13:59
|
|
|
Re: Enhance SnapshotDeletionPolicy to allow taking multiple snapshots - Lucene - [mail # dev]
|
|
...That's an interesting point ... I still think we should use IDs though, because the application that uses this (like me :)) may want to persist the snapshots used elsewhere, in case th...
|
|
|
Author: Shai Erera,
2010-04-27, 15:18
|
|
|
Re: SnapshotDeletionPolicy throws NPE if no commit happened - Lucene - [mail # dev]
|
|
...BTW, even if it's a stupid thing to do, someone can today create SDP and call snapshot without ever creating IW. And it's not an impossible scenario . Consider a backup-aware application whi...
|
|
|
Author: Shai Erera,
2010-04-15, 08:34
|
|
|
Re: SnapshotDeletionPolicy throws NPE if no commit happened - Lucene - [mail # dev]
|
|
...Well ... one can still call commit() or close() right after IW creation. An d this is a very rare case to be hit by. Was just asking about whether we wan t to add an explicit and clear prote...
|
|
|
Author: Shai Erera,
2010-04-15, 07:36
|
|
|
SnapshotDeletionPolicy throws NPE if no commit happened - Lucene - [mail # dev]
|
|
...SDP throws NPE if the index includes no commits, but snapshot() is called. This is an extreme case, but can happen if one takes snapshots (for backup purposes for example) in a separate code...
|
|
|
Author: Shai Erera,
2010-04-15, 07:16
|
|
|
[LUCENE-4621] FacetIndexing/SearchParams house cleaning - Lucene - [issue]
|
|
...FacetIndexingParams lets you configure few things such as OrdinalPolicy, PathPolicy and partitionSize. However, in order to set them you must extend DefaultFacetIndexingParams and override...
|
|
|
http://issues.apache.org/jira/browse/LUCENE-4621
Author: Shai Erera,
2013-01-24, 06:33
|
|
|
[LUCENE-3138] IW.addIndexes should fail fast if an index is too old/new - Lucene - [issue]
|
|
... during commit() or segment merges. We should check that up front and fail fast.
This issue is relevant only to 4.0 at the moment, which will not support 2.x indexes anymore....
|
|
|
http://issues.apache.org/jira/browse/LUCENE-3138
Author: Shai Erera,
2013-01-29, 05:55
|
|
|
[LUCENE-4610] Implement a NoParentsAccumulator - Lucene - [issue]
|
|
...Mike experimented with encoding just the exact categories ordinals on LUCENE-4602, and I added OrdinalPolicy.NO_PARENTS, with a comment saying that this requires a special Facets...
|
|
|
http://issues.apache.org/jira/browse/LUCENE-4610
Author: Shai Erera,
2013-01-21, 20:03
|
|
|
|
