[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 686 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/686/ 3 tests failed. REGRESSION: org.apache.solr.handler.dataimport.TestSqlEntityProcessorDelta3.testCompositePk_DeltaImport_nodelta Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Ex

[JENKINS] Lucene-Solr-trunk-Linux-Java7-64 - Build # 159 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java7-64/159/ 1 tests failed. REGRESSION: org.apache.solr.handler.dataimport.TestSqlEntityProcessorDelta3.testCompositePk_DeltaImport_nodelta Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Ex

[JENKINS] Lucene-Solr-trunk-Windows-Java6-64 - Build # 398 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java6-64/398/ 1 tests failed. REGRESSION: org.apache.solr.search.TestSort.testRandomFieldNameSorts Error Message: Over 0.2% oddities in test: 13/6395 have func/query parsing semenatics gotten broader? Stack Trace: java.la

[jira] [Commented] (SOLR-3505) Detect and report when the limit for maximum number of documents in a single index is exceeded

[ https://issues.apache.org/jira/browse/SOLR-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288277#comment-13288277 ] Jack Krupansky commented on SOLR-3505: -- Similar to LUCENE-4105, it would greatly simpl

[jira] [Commented] (LUCENE-4105) Detect and report when the limit for maximum number of documents in a single index is exceeded

[ https://issues.apache.org/jira/browse/LUCENE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288274#comment-13288274 ] Jack Krupansky commented on LUCENE-4105: To facilitate testing, I would propose a

[jira] [Created] (SOLR-3505) Detect and report when the limit for maximum number of documents in a single index is exceeded

Jack Krupansky created SOLR-3505: Summary: Detect and report when the limit for maximum number of documents in a single index is exceeded Key: SOLR-3505 URL: https://issues.apache.org/jira/browse/SOLR-3505

[jira] [Created] (LUCENE-4105) Detect and report when the limit for maximum number of documents in a single index is exceeded

Jack Krupansky created LUCENE-4105: -- Summary: Detect and report when the limit for maximum number of documents in a single index is exceeded Key: LUCENE-4105 URL: https://issues.apache.org/jira/browse/LUCENE-4105

[jira] [Commented] (SOLR-3504) Clearly document the limit for the maximum number of documents in a single index

[ https://issues.apache.org/jira/browse/SOLR-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288266#comment-13288266 ] Jack Krupansky commented on SOLR-3504: -- Solr has a number of interfaces for adding doc

Re: What is the maximum document number?

Double oops... it is Integer.MAX_VALUE, not Integer.MAX_INT. -- Jack Krupansky From: Jack Krupansky Sent: Sunday, June 03, 2012 5:11 PM To: dev@lucene.apache.org Subject: Re: What is the maximum document number? Oops, I indicated that Integer.MAX_INT was 2^30-1, but it is 2^31-1 or 2,147,483,

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #392

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Created] (SOLR-3504) Clearly document the limit for the maximum number of documents in a single index

Jack Krupansky created SOLR-3504: Summary: Clearly document the limit for the maximum number of documents in a single index Key: SOLR-3504 URL: https://issues.apache.org/jira/browse/SOLR-3504 Project:

[jira] [Updated] (LUCENE-4104) Clearly document the limit for maximum number of documents in a single index

[ https://issues.apache.org/jira/browse/LUCENE-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Krupansky updated LUCENE-4104: --- Description: Although the "int" in a number of APIs strongly suggests the approximate limit

[jira] [Commented] (LUCENE-4104) Clearly document the limit for maximum number of documents in a single index

[ https://issues.apache.org/jira/browse/LUCENE-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288263#comment-13288263 ] Jack Krupansky commented on LUCENE-4104: I propose to add these constants to Inde

[jira] [Created] (LUCENE-4104) Clearly document the limit for maximum number of documents in a single index

Jack Krupansky created LUCENE-4104: -- Summary: Clearly document the limit for maximum number of documents in a single index Key: LUCENE-4104 URL: https://issues.apache.org/jira/browse/LUCENE-4104 Proj

Re: What is the maximum document number?

Oops, I indicated that Integer.MAX_INT was 2^30-1, but it is 2^31-1 or 2,147,483,647. So the largest document number in Lucene would be 2,147,483,646 and the largest number (count) of documents would be 2,147,483,647. -- Jack Krupansky From: Jack Krupansky Sent: Sunday, June 03, 2012 4:09 PM T

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #391

See -- [...truncated 16582 lines...] [junit4] 2>at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.ja

Re: What is the maximum document number?

The javadoc for IR.maxDoc refers to “largest possible document number”, but the word “possible” is confusing. Superficially it sounds like the largest document number that Lucene can ever assign, but really it is simply the “largest document number in the index at the moment, including deleted d

Re: What is the maximum document number?

Hi, In fact maxDoc is not the maximum, it is also a count. If no deletions are in an index, maxDoc==numDocs. That's unfortunately how it is, maybe we should rename that in 4.0. Uwe -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de Jack Krupansky schrieb: Doing a li

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #390

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Comment Edited] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287627#comment-13287627 ] Steven Rowe edited comment on LUCENE-4092 at 6/3/12 7:07 PM: -

[jira] [Updated] (LUCENE-3892) Add a useful intblock postings format (eg, FOR, PFOR, PFORDelta, Simple9/16/64, etc.)

[ https://issues.apache.org/jira/browse/LUCENE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Jiang updated LUCENE-3892: -- Attachment: LUCENE-3892_pfor.patch Ah, just cannot wait for a performance optimization! This version

[jira] [Updated] (LUCENE-4103) AnalyzerQueryNodeProcessor throws a class cast exception with the RegexpQueryNode

[ https://issues.apache.org/jira/browse/LUCENE-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Truemper updated LUCENE-4103: Attachment: 0001-Fix-for-the-flexible-regexp-parsing.patch A patch in GIT format that can

What is the maximum document number?

Doing a little more research on document numbers, I had thought that the maximum document number was 2^30-1 or Integer.MAX_INT, but... I see that IndexReader.numDocs, maxDoc, and the corresponding IndexWriter methods return the number of documents as an int, so since document numbers start at ze

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #389

See -- [...truncated 16408 lines...] [junit4] [junit4] Suite: org.apache.solr.core.TestConfig [junit4] Completed in 0.43s, 7 tests [junit4] [junit4] Suite: o

[jira] [Updated] (LUCENE-4103) AnalyzerQueryNodeProcessor throws a class cast exception with the RegexpQueryNode

[ https://issues.apache.org/jira/browse/LUCENE-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Truemper updated LUCENE-4103: Fix Version/s: 4.0 Affects Version/s: 4.0 > AnalyzerQueryNodeProcessor throws

[jira] [Created] (LUCENE-4103) AnalyzerQueryNodeProcessor throws a class cast exception with the RegexpQueryNode

Daniel Truemper created LUCENE-4103: --- Summary: AnalyzerQueryNodeProcessor throws a class cast exception with the RegexpQueryNode Key: LUCENE-4103 URL: https://issues.apache.org/jira/browse/LUCENE-4103

Missing javadoc for IndexWriter.hasDeletions

There is no javadoc for IndexWriter.hasDeletions. I would have expected it to be the same as for IndexReader: /** Returns true if any documents have been deleted */ Although, I think both should also say “since the most recent merge”. -- Jack Krupansky

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288202#comment-13288202 ] Jack Krupansky commented on SOLR-3503: -- Ultimately it may simply come down to doing be

[jira] [Resolved] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson resolved SOLR-3503. -- Resolution: Won't Fix Jack: Go ahead and have a whack at it if you want, but given that if one

[jira] [Reopened] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson reopened SOLR-3503: -- Changing to "won't fix" > Make SnowballPorterFilterFactory (and other stemmers?) Mu

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288174#comment-13288174 ] Jack Krupansky commented on SOLR-3503: -- Or are you just trying to trick me into doing

[jira] [Resolved] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson resolved SOLR-3503. -- Resolution: Invalid Gaaah! That'll teach me to put up a JIRA when I haven't had enough coffee. I

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288167#comment-13288167 ] Jack Krupansky commented on SOLR-3503: -- It could be tricky, but it could work, but use

RE: svn commit: r820071 - in /websites: production/lucene/content/ production/lucene/content/core/ production/lucene/content/solr/ staging/lucene/trunk/content/ staging/lucene/trunk/content/core/ stag

I programmed my imap server filters to redirect them to trash :-) - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Jack Krupansky [mailto:j...@basetechnology.com] > Sent: Sunday, June 03, 2012 3:18 PM > To

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288164#comment-13288164 ] Jack Krupansky commented on LUCENE-4101: Superficially, the new concept of a fiel

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288157#comment-13288157 ] Robert Muir commented on LUCENE-4101: - {quote} I set it to blocker because I think th

Re: svn commit: r820071 - in /websites: production/lucene/content/ production/lucene/content/core/ production/lucene/content/solr/ staging/lucene/trunk/content/ staging/lucene/trunk/content/core/ stag

I see many of these messages every day and they are all virtually identical - indicating "(empty)" modifications - but with new revision numbers for web pages on staging and production. Sometimes the modifications are not "(empty)", suggesting that the empties are for failed builds and only on

[jira] [Commented] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288155#comment-13288155 ] Robert Muir commented on SOLR-3503: --- most stemmers use length of the string / syllable co

[jira] [Created] (SOLR-3503) Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware

Erick Erickson created SOLR-3503: Summary: Make SnowballPorterFilterFactory (and other stemmers?) MultiTermAware Key: SOLR-3503 URL: https://issues.apache.org/jira/browse/SOLR-3503 Project: Solr

[jira] [Assigned] (SOLR-3441) Make ElisionFilterFactory MultiTermAware

[ https://issues.apache.org/jira/browse/SOLR-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson reassigned SOLR-3441: Assignee: Erick Erickson > Make ElisionFilterFactory MultiTermAware > --

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #382

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (LUCENE-4102) SuppressCodecs doesnt work with -Dtests.postingsformat

[ https://issues.apache.org/jira/browse/LUCENE-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288143#comment-13288143 ] Dawid Weiss commented on LUCENE-4102: - Per-method cause from suite-level assumption f

[jira] [Updated] (LUCENE-4102) SuppressCodecs doesnt work with -Dtests.postingsformat

[ https://issues.apache.org/jira/browse/LUCENE-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss updated LUCENE-4102: Attachment: LUCENE-4102.patch I'd just move all the suppression checks to the class rule -- it is

[jira] [Commented] (LUCENE-2858) Separate SegmentReaders (and other atomic readers) from composite IndexReaders

[ https://issues.apache.org/jira/browse/LUCENE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288135#comment-13288135 ] Michael McCandless commented on LUCENE-2858: bq. This explains the change bac

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #381

See -- [...truncated 10458 lines...] [junit4] Completed in 1.25s, 1 test [junit4] [junit4] Suite: org.apache.solr.handler.XmlUpdateRequestHandlerTest [junit4] Com

[jira] [Commented] (LUCENE-2858) Separate SegmentReaders (and other atomic readers) from composite IndexReaders

[ https://issues.apache.org/jira/browse/LUCENE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288133#comment-13288133 ] Uwe Schindler commented on LUCENE-2858: --- Thanks Mike for taking care. For me this l

[jira] [Commented] (LUCENE-2858) Separate SegmentReaders (and other atomic readers) from composite IndexReaders

[ https://issues.apache.org/jira/browse/LUCENE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288129#comment-13288129 ] Michael McCandless commented on LUCENE-2858: bq. Not entirely sure why but it

[jira] [Updated] (LUCENE-4100) Maxscore - Efficient Scoring

[ https://issues.apache.org/jira/browse/LUCENE-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Pohl updated LUCENE-4100: Description: At Berlin Buzzwords 2012, I will be presenting 'maxscore', an efficient algorithm fi

Re: Suppressing list doesn't take effect when -Dtests.postingsformat is used

Robert's patch looks good to me. Perhaps we could just move the entire assumption to that rule (I don't have the code open so I don't know where this is called, but I think it should be determined as soon as possible and once). Dawid On Sun, Jun 3, 2012 at 9:54 AM, Uwe Schindler wrote: >> The ac

Re: seeing stdout when running "ant test"?

On Sat, Jun 2, 2012 at 11:37 AM, Dawid Weiss wrote: >> Thanks Dawid!  -Dtests.showSuccess=true is what I was looking for ... >> I'll add it to the wiki. > > Thanks, I'm wiki-challenged. There is also command-line help readily > available if you type: > > ant test-help > >     [echo] # Include addi

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288123#comment-13288123 ] Michael McCandless commented on LUCENE-4101: Sorry, I don't intend to rush th

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java7-64 #213

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288112#comment-13288112 ] Uwe Schindler commented on LUCENE-4101: --- Hi, I am strong +1 for adding the field tw

RE: Suppressing list doesn't take effect when -Dtests.postingsformat is used

> The actual source of the problem is that suppression applies to codec.getName > and enforcing a TEST_POSTINGSFORMAT means Lucene40Codec is created > which always returns Lucene40 from getName(). A simple fix would be to allow > changing the returned name for Lucene40. I don't think we should do

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288109#comment-13288109 ] Simon Willnauer commented on LUCENE-4101: - bq. I'm not sure we should rush it in:

Re: Suppressing list doesn't take effect when -Dtests.postingsformat is used

On Sat, Jun 2, 2012 at 11:16 PM, Dawid Weiss wrote: > The actual source of the problem is that suppression applies to > codec.getName and enforcing a TEST_POSTINGSFORMAT means  Lucene40Codec > is created which always returns Lucene40 from getName(). A simple fix > would be to allow changing the re

[jira] [Created] (LUCENE-4102) SuppressCodecs doesnt work with -Dtests.postingsformat

Robert Muir created LUCENE-4102: --- Summary: SuppressCodecs doesnt work with -Dtests.postingsformat Key: LUCENE-4102 URL: https://issues.apache.org/jira/browse/LUCENE-4102 Project: Lucene - Java

[jira] [Updated] (LUCENE-4102) SuppressCodecs doesnt work with -Dtests.postingsformat

[ https://issues.apache.org/jira/browse/LUCENE-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4102: Attachment: LUCENE-4102.patch simple patch > SuppressCodecs doesnt work with -Dte

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java7-64 #212

See -- [...truncated 14406 lines...] [junit4] Suite: org.apache.solr.core.TestXIncludeConfig [junit4] Completed in 0.67s, 1 test [junit4] [junit4] Suite: org.apac