| clear query|facets|time |
Search criteria: TieredMergePolicy.
Results from 81 to 90 from
174 (0.3s).
|
|
|
Loading phrases to help you
refine your search...
|
|
Re: Facet examples javadoc missing in 4.0? - Lucene - [mail # dev]
|
|
... one stands out. bq. Can we merge these examples into the demo/ module? We tried that in LUCENE-3998 without success. The problem are facet tests which depend on data that exists...
|
|
|
Author: Shai Erera,
2012-11-24, 17:18
|
|
|
Re: [JENKINS] Lucene-Solr-tests-only-3.x - Build # 9438 - Failure - Lucene - [mail # dev]
|
|
...Ok that was easy - the test expects docs to be in some order, so changed it to enforce log-merge-policy. I'll commit a fix to 3x and trunk. Shai On Sun, Jul 10, 2011 at 8:39 AM, Shai...
|
|
|
Author: Shai Erera,
2011-07-10, 05:44
|
|
|
[LUCENE-3061] Open IndexWriter API to allow custom MergeScheduler implementation - Lucene - [issue]
|
|
...IndexWriter's getNextMerge() and merge(OneMerge) are package-private, which makes it impossible for someone to implement his own MergeScheduler. We should open up these API, as well as any...
|
|
|
http://issues.apache.org/jira/browse/LUCENE-3061
Author: Shai Erera,
2011-06-03, 17:37
|
|
|
Re: ConcurrentMergeScheduler may spawn MergeThreads forever - Lucene - [mail # dev]
|
|
... I will check the code again, but I remember that after commenting it, the only compile errors I saw were from MergeThread adding the exception ... perhaps I'm missing something, so I'll re...
|
|
...-check the code. I understand your point now - merging is an internal process to IW, therefore there's no real user to notify on errors (e.g., even if IW knew there is an error, what would it do exactly...
|
[+ show more]
[- hide]
| ...?), and I guess keep trying to execute the merges is reasonable (while throwing the exceptions further - in hope that the user code will catch those and do something with them). BTW, what... |
| ... be in a state prior to the merge, or at least prior to the merge that failed? I think that sleeping in case of exceptions makes sense .. in case of IO errors that are temporary, this will not spawn... |
|
|
Author: Shai Erera,
2009-04-28, 13:27
|
|
|
Re: ConcurrentMergeScheduler may spawn MergeThreads forever - Lucene - [mail # dev]
|
|
...I hope that I don't make a complete fool of myself, but I'm talking about this: private List exceptions = new ArrayList(); and this (MergeThread.run()): synchronized(ConcurrentMerge...
|
|
|
Author: Shai Erera,
2009-04-28, 20:00
|
|
|
Re: ConcurrentMergeScheduler may spawn MergeThreads forever - Lucene - [mail # dev]
|
|
...Every merge hit the exception, yes. And actually, the exceptions list is not used anywhere besides MT adding the exception to the list. That's why I was curious why it's there. I still...
|
|
|
Author: Shai Erera,
2009-04-28, 12:28
|
|
|
Re: ConcurrentMergeScheduler may spawn MergeThreads forever - Lucene - [mail # dev]
|
|
...Thanks ! On Tue, Apr 28, 2009 at 11:48 PM, Michael McCandless wrote: ...
|
|
|
Author: Shai Erera,
2009-04-29, 03:31
|
|
|
Re: Source Control - Lucene - [mail # dev]
|
|
... to the branch, without worrying about breaking the main branch or nightly builds. When it's time, the changes will be merged to the main branch. But what we lack today is true collaboration -- allow all...
|
|
|
Author: Shai Erera,
2012-10-28, 12:04
|
|
|
Test failure on 3x - Lucene - [mail # dev]
|
|
...I ran tests on 3x today and hit this: [junit] Testsuite: org.apache.lucene.index.TestIndexWriterMergePolicy [junit] Testcase: testMaxBufferedDocsChange(org.apache.lucene.index.TestIndexWriterMergePolicy...
|
|
...] at org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1008) [junit] at org.apache.lucene.index.TestIndexWriterMergePolicy.checkInvariants(TestIndexWriterMergePolicy...
|
[+ show more]
[- hide]
| ....java:221) [junit] at org.apache.lucene.index.TestIndexWriterMergePolicy.testMaxBufferedDocsChange(TestIndexWriterMergePolicy.java:168) [junit] [junit] [junit] Tests run: 6... |
| ..., Failures: 1, Errors: 0, Time elapsed: 2.777 sec [junit] [junit] ------------- Standard Error ----------------- [junit] NOTE: reproduce with: ant test -Dtestcase=TestIndexWriterMergePolicy... |
| ... tests run in this JVM: [junit] [TestCharArrayMap, TestLengthFilter, TestTeeSinkTokenFilter, TestBinaryDocument, TestByteSlices, TestDocumentWriter, TestIndexReaderClone, TestIndexWriterMergePolicy... |
|
|
Author: Shai Erera,
2011-03-28, 05:00
|
|
|
Re: IndexWriter.close() performance issue - Lucene - [mail # user]
|
|
... or less the same (i.e., comparable # of docs and total # bytes indexed), then you should not see a performance difference between closes. * Consults the MergePolicy and runs any merges it returns...
|
|
... merges returned by MergePolicy. writer.waitForMerges(); // if you use ConcurrentMergeScheduler, the above call returns immediately, not waiting for the merges to finish. writer...
|
[+ show more]
[- hide]
| ....close(); // at this point, commit + merging has finished, so it does very little. As your index grows in size, so does its # of segments, and the segments size as well. So tweaking some parameters on the MergePolicy... |
| .... 3) If you want to control when the merges are run, you can open IndexWriter with NoMergePolicy, which always returns 0 merges to perform, or NoMergeScheduler which never executes merges... |
| ... as candidates. * Waits for the merges to finish. Roughly, IndexWriter.close() can be substituted w/: writer.commit(false); // commits the changes, but does not run merges. writer.maybeMerge(); // runs... |
|
|
Author: Shai Erera,
2010-11-02, 09:20
|
|
|
|
