Solr-trunk - Build # 1346 - Failure

Build: https://hudson.apache.org/hudson/job/Solr-trunk/1346/ All tests passed Build Log (for compile errors): [...truncated 20163 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

[jira] Commented: (LUCENE-2694) MTQ rewrite + weight/scorer init should be single pass

[ https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972758#action_12972758 ] Michael McCandless commented on LUCENE-2694: If I force scoring BQ rewrite for

Re: Do we want 'nocommit' to fail the commit?

+1 this would be great :) Mike On Fri, Dec 17, 2010 at 10:45 PM, Shai Erera ser...@gmail.com wrote: Hi Out of curiosity, I searched if we can have a nocommit comment in the code fail the commit. As far as I see, we try to avoid accidental commits (of say debug messages) by putting a nocommit

[jira] Commented: (LUCENE-2818) abort() method for IndexOutput

[ https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972763#action_12972763 ] Michael McCandless commented on LUCENE-2818: +1 I think this'd be a good

Re: Do we want 'nocommit' to fail the commit?

But. Er. What if we happen to have nocommit in a string, or in some docs, or as a name of variable? On Sat, Dec 18, 2010 at 12:47, Michael McCandless luc...@mikemccandless.com wrote: +1 this would be great :) Mike On Fri, Dec 17, 2010 at 10:45 PM, Shai Erera ser...@gmail.com wrote: Hi Out

Re: Do we want 'nocommit' to fail the commit?

I like this idea, too. But I think we have no control on this, it would be as complicated as the mergeprops... What we have: Hudson halfly hour builds fail when svn contains commits, so you see it latest 30 Min later. Uwe Shai Erera ser...@gmail.com schrieb: Hi Out of curiosity, I

[jira] Commented: (LUCENE-2818) abort() method for IndexOutput

[ https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972764#action_12972764 ] Earwin Burrfoot commented on LUCENE-2818: - bq. Can abort() have a default impl in

[jira] Commented: (LUCENE-2818) abort() method for IndexOutput

[ https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972765#action_12972765 ] Earwin Burrfoot commented on LUCENE-2818: - bq. I think we can make a default impl

[jira] Updated: (LUCENE-2818) abort() method for IndexOutput

[ https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Earwin Burrfoot updated LUCENE-2818: Priority: Minor (was: Major) This change is really minor, but I think, convinient. You

[jira] Commented: (LUCENE-2814) stop writing shared doc stores across segments

[ https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972767#action_12972767 ] Michael McCandless commented on LUCENE-2814: Patch looks great! Nice work

[jira] Commented: (LUCENE-2694) MTQ rewrite + weight/scorer init should be single pass

[ https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972769#action_12972769 ] Uwe Schindler commented on LUCENE-2694: --- I have also some things: - We currently

[jira] Issue Comment Edited: (LUCENE-2694) MTQ rewrite + weight/scorer init should be single pass

[ https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972769#action_12972769 ] Uwe Schindler edited comment on LUCENE-2694 at 12/18/10 5:43 AM:

Re: Do we want 'nocommit' to fail the commit?

I haven't seen nocommit in the code, neither as String nor as member. But we can decide that we do @nocommit@ or something, which is less likely to be contained in code :). Uwe, I didn't understand your response - do you mean that if the code contains a 'nocommit' in any of the .java files,

[jira] Updated: (LUCENE-2814) stop writing shared doc stores across segments

[ https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Earwin Burrfoot updated LUCENE-2814: Attachment: LUCENE-2814.patch Synced to trunk. bq. Also, on the nocommit on exc in

[jira] Commented: (LUCENE-2818) abort() method for IndexOutput

[ https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972772#action_12972772 ] Shai Erera commented on LUCENE-2818: I offered a default impl just to not break the

[jira] Created: (LUCENE-2819) LuceneTestCase's check for uncaught exceptions in threads causes collateral damage?

LuceneTestCase's check for uncaught exceptions in threads causes collateral damage? --- Key: LUCENE-2819 URL: https://issues.apache.org/jira/browse/LUCENE-2819 Project:

[jira] Commented: (LUCENE-2819) LuceneTestCase's check for uncaught exceptions in threads causes collateral damage?

[ https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972776#action_12972776 ] Robert Muir commented on LUCENE-2819: - I think this is the problem: lets say the main

[jira] Updated: (LUCENE-2694) MTQ rewrite + weight/scorer init should be single pass

[ https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2694: -- Attachment: LUCENE-2694-FTE.patch Here just the patch for a correct behaving

[jira] Updated: (LUCENE-2819) LuceneTestCase's check for uncaught exceptions in threads causes collateral damage?

[ https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2819: --- Attachment: LUCENE-2819.patch Attaching current patch; includes lots of noise and

Lucene-Solr-tests-only-trunk - Build # 2691 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2691/ 4 tests failed. FAILED: org.apache.solr.util.SolrPluginUtilsTest.testAddToNamedListPrimitiveTypes Error Message: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until

[jira] Updated: (LUCENE-2819) LuceneTestCase's check for uncaught exceptions in threads causes collateral damage?

[ https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2819: Attachment: LUCENE-2819.patch I worked on mike's patch a bit... here's an updated version. I

[jira] Commented: (LUCENE-2818) abort() method for IndexOutput

[ https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972816#action_12972816 ] Michael McCandless commented on LUCENE-2818: I think a bw compat exception is

[jira] Created: (SOLR-2290) the termsInfosDivisor for readers opened by indexWriter should be configurable in Solr

the termsInfosDivisor for readers opened by indexWriter should be configurable in Solr -- Key: SOLR-2290 URL: https://issues.apache.org/jira/browse/SOLR-2290

Re: Lucene-3.x - Build # 214 - Failure

I committed a fix for this. I think there was actually only one failure, which cascaded due still running threads spilling over to other test methods (LUCENE-2819). The one failure was caused by LUCENE-2811 (SI tracks hasVectors) in addIndexes(Directory[]); we were failing to copy over the

[jira] Updated: (LUCENE-2819) LuceneTestCase's check for uncaught exceptions in threads causes collateral damage?

[ https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2819: Attachment: LUCENE-2819.patch here's an updated patch, I think its much better. The core tests

[jira] Updated: (LUCENE-2723) Speed up Lucene's low level bulk postings read API

[ https://issues.apache.org/jira/browse/LUCENE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated LUCENE-2723: - Attachment: LUCENE-2723_openEnum.patch Here's a small patch that may be sufficient to enable

[jira] Commented: (LUCENE-2814) stop writing shared doc stores across segments

[ https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972842#action_12972842 ] Michael McCandless commented on LUCENE-2814: OK I committed to trunk. I'll

[jira] Commented: (SOLR-2290) the termsInfosDivisor for readers opened by indexWriter should be configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972847#action_12972847 ] Jason Rutherglen commented on SOLR-2290: Tom, I think this can be generified to use

[jira] Commented: (LUCENE-2814) stop writing shared doc stores across segments

[ https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972850#action_12972850 ] Jason Rutherglen commented on LUCENE-2814: -- bq. backporting to 3.x... Out of

[jira] Commented: (LUCENE-2500) A Linux-specific Directory impl that bypasses the buffer cache

[ https://issues.apache.org/jira/browse/LUCENE-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972855#action_12972855 ] Jason Rutherglen commented on LUCENE-2500: -- DirectIOLinuxDirectory is in trunk

Lucene-Solr-tests-only-trunk - Build # 2706 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2706/ 1 tests failed. REGRESSION: org.apache.lucene.search.TestRemoteCachingWrapperFilter.testTermRemoteFilter Error Message: Some threads threw uncaught exceptions! Stack Trace: junit.framework.AssertionFailedError:

Lucene-Solr-tests-only-trunk - Build # 2707 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2707/ 1 tests failed. FAILED: org.apache.lucene.search.TestRemoteCachingWrapperFilter.testTermRemoteFilter Error Message: Some threads threw uncaught exceptions! Stack Trace: junit.framework.AssertionFailedError: Some

Lucene-Solr-tests-only-trunk - Build # 2708 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2708/ 1 tests failed. FAILED: org.apache.lucene.search.TestRemoteCachingWrapperFilter.testTermRemoteFilter Error Message: Some threads threw uncaught exceptions! Stack Trace: junit.framework.AssertionFailedError: Some

[jira] Created: (LUCENE-2820) CMS fails to cleanly stop threads

CMS fails to cleanly stop threads - Key: LUCENE-2820 URL: https://issues.apache.org/jira/browse/LUCENE-2820 Project: Lucene - Java Issue Type: Bug Reporter: Michael McCandless

[jira] Commented: (LUCENE-2723) Speed up Lucene's low level bulk postings read API

[ https://issues.apache.org/jira/browse/LUCENE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972869#action_12972869 ] Michael McCandless commented on LUCENE-2723: Looks good Yonik! Speed up

[jira] Created: (LUCENE-2822) TimeLimitingCollector starts thread in static {} with no way to stop them

TimeLimitingCollector starts thread in static {} with no way to stop them - Key: LUCENE-2822 URL: https://issues.apache.org/jira/browse/LUCENE-2822 Project: Lucene - Java

[jira] Created: (LUCENE-2821) FilterManager starts threads with no way to stop, and should be in contrib/remote, not core

FilterManager starts threads with no way to stop, and should be in contrib/remote, not core --- Key: LUCENE-2821 URL: https://issues.apache.org/jira/browse/LUCENE-2821

[jira] Created: (LUCENE-2823) contrib/demo's tests leave threads running

contrib/demo's tests leave threads running -- Key: LUCENE-2823 URL: https://issues.apache.org/jira/browse/LUCENE-2823 Project: Lucene - Java Issue Type: Bug Components: Examples

[jira] Updated: (LUCENE-2820) CMS fails to cleanly stop threads

[ https://issues.apache.org/jira/browse/LUCENE-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2820: --- Attachment: LUCENE-2820.patch Patch. I changed CMS.sync to .join() to any

[jira] Created: (SOLR-2291) JSONWriter.writeSolrDocument() does not respect its SetString returnFields parameter.

JSONWriter.writeSolrDocument() does not respect its SetString returnFields parameter. --- Key: SOLR-2291 URL: https://issues.apache.org/jira/browse/SOLR-2291

[jira] Updated: (SOLR-2291) JSONWriter.writeSolrDocument() does not respect its SetString returnFields parameter.

[ https://issues.apache.org/jira/browse/SOLR-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ahmet Arslan updated SOLR-2291: --- Attachment: SOLR-2291.patch JSONWriter.writeSolrDocument() does not respect its SetString

SolrPluginUtils.docListToSolrDocumentList loads all stored fields

Hello, Regardless of SetString fields parameter, SolrPluginUtils#docListToSolrDocumentList method loads all of the stored fields. Shouldn't it just load the fields given in the set? Should I file a jira ticket? When small bug in TestCase is seen what is the preffered way to inform it? Open

[jira] Commented: (LUCENE-2816) MMapDirectory speedups

[ https://issues.apache.org/jira/browse/LUCENE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972880#action_12972880 ] Robert Muir commented on LUCENE-2816: - committed revision 1050737. I'll wait a bit for

[jira] Resolved: (LUCENE-2819) LuceneTestCase's check for uncaught exceptions in threads causes collateral damage?

[ https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-2819. - Resolution: Fixed committed and merged to 3.x in 3.x i kept the test code in CMS (even though