Re: from 2.2.0 to 2.3.0

rt compareToLastTerm(fieldNumber, termText, termTextStart, termTextLength) < 0 || (isIndex && termTextLength == 0 && lastTermTextLength == 0); Can you help me? Sergey Kabashnyuk ----- -- -- To unsubscribe, e-mail: [EMAI

Re: from 2.2.0 to 2.3.0

gt; (RepositoryImpl.java:348) >>>>at >>>> org.apache.jackrabbit.core.RepositoryImpl.create >>>> (RepositoryImpl.java:557) >>>>at >>>> org.springmodules.jcr.jackrabbit.RepositoryFactoryBean.createReposit >>>> or >>>> y

Re: from 2.2.0 to 2.3.0

tart, termTextLength) < 0 || (isIndex && termTextLength == 0 && lastTermTextLength == 0); Can you help me? Sergey Kabashnyuk --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTEC

Re: from 2.2.0 to 2.3.0

tractAutowireCapableBeanF >> actory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1333) >> at >> org.springframework.beans.factory.support.AbstractAutowireCapableBeanF >> actory.initializeBean(AbstractAutowireCapableBeanFactory.java:1299) >>

Re: from 2.2.0 to 2.3.0

l: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/from--2.2.0- to-2.3.0-tp15501449p16323371.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. -

Re: from 2.2.0 to 2.3.0

t; lastTermTextLength == 0); > > Can you help me? > > Sergey Kabashnyuk > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message

Re: from 2.2.0 to 2.3.0

Sergey Kabashnyuk wrote: On Fri, 15 Feb 2008 16:31:07 +0200, Michael McCandless <[EMAIL PROTECTED]> wrote: OK I found one case that can cause the assert to trip incorrectly. Are you using empty string field names? Not. May be empty content of the field. Hmmm, ok. Empty content is fine

Re: from 2.2.0 to 2.3.0

On Fri, 15 Feb 2008 16:31:07 +0200, Michael McCandless <[EMAIL PROTECTED]> wrote: OK I found one case that can cause the assert to trip incorrectly. Are you using empty string field names? Not. May be empty content of the field. I have another question. I see you use asserts in code 2.3.0

Re: from 2.2.0 to 2.3.0

OK I found one case that can cause the assert to trip incorrectly. Are you using empty string field names? I'll open a Jira issue & fix it on the 2.3 branch (so this is fixed in 2.3.1). Thanks for reporting this! Mike Sergey Kabashnyuk wrote: stack trace java.lang.AssertionError

Re: from 2.2.0 to 2.3.0

CheckIndex tool is in the 2.3 JAR. Just make sure the JAR is on your CLASSPATH then run: java org.apache.lucene.index.CheckIndex However, from that stack trace, this is not a corruption issue in your existing index. My guess is you would hit this same exception if you started from a

Re: from 2.2.0 to 2.3.0

stack trace java.lang.AssertionError at org.apache.lucene.index.TermInfosWriter.add(TermInfosWriter.java:143) at org.apache.lucene.index.DocumentsWriter.appendPostings(DocumentsWriter.java:2290) at org.apache.lucene.index.DocumentsWriter.writeSegment(DocumentsWriter.j

Re: from 2.2.0 to 2.3.0

Can you provide the full stack trace, and any details of what you were doing when you tripped that assert? Another thing to try is to run the org.apache.lucene.index.CheckIndex tool (new in 2.3) to check your 2.2 index. It's possible your 2.2 index has some undetected corruption which th

from 2.2.0 to 2.3.0

Hi I want to update from lucene 2.2.0 to 2.3.0 but I have assert it TermInfosWriter line 143. What is it mean assert compareToLastTerm(fieldNumber, termText, termTextStart, termTextLength) < 0 || (isIndex && termTextLength == 0 && lastTermTextLength == 0); Can you help me? Sergey Kabashnyuk -