|
»
»
»
from 2.2.0 to 2.3.0
|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
 |
from 2.2.0 to 2.3.0
by Sergey Kabashnyuk-3
::
Rate this Message:
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 --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
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 this new assert is detecting. Mike Sergey Kabashnyuk wrote: > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by Sergey Kabashnyuk-3
::
Rate this Message:
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.java:1985) at org.apache.lucene.index.DocumentsWriter.flush(DocumentsWriter.java:539) at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:2497) at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:2397) at org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:1204) at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1178) at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1153) Where I can find CheckIndex.tool ? Sergey Kabashnyuk > > 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 this new assert is detecting. > > Mike > > Sergey Kabashnyuk wrote: > >> 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 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > -- Отправлено M2, революционной почтовой программой Opera: http://www.opera.com/mail/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
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 <indexDirectory> 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 new index because it's being hit when flushing a new segment (not merging old ones). How many documents are you adding before closing the writer? Are you using multiple threads to add documents? What kinds of documents are you adding? Can you try disabling asserts, then try to build your index, then run CheckIndex on the resulting index? It's possible this is an over- aggressive assert. I'll go scrutinize that code... Mike Sergey Kabashnyuk wrote: > 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.java:1985) > at org.apache.lucene.index.DocumentsWriter.flush > (DocumentsWriter.java:539) > at org.apache.lucene.index.IndexWriter.doFlush > (IndexWriter.java:2497) > at org.apache.lucene.index.IndexWriter.flush > (IndexWriter.java:2397) > at org.apache.lucene.index.IndexWriter.closeInternal > (IndexWriter.java:1204) > at org.apache.lucene.index.IndexWriter.close > (IndexWriter.java:1178) > at org.apache.lucene.index.IndexWriter.close > (IndexWriter.java:1153) > > Where I can find CheckIndex.tool ? > > Sergey Kabashnyuk > >> >> 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 this new assert is detecting. >> >> Mike >> >> Sergey Kabashnyuk wrote: >> >>> 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 >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: java-user-unsubscribe@... >>> For additional commands, e-mail: java-user-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> > > > > -- > Отправлено M2, революционной > почтовой программой Opera: http://www.opera.com/ > mail/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
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 > 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.java:1985) > at org.apache.lucene.index.DocumentsWriter.flush > (DocumentsWriter.java:539) > at org.apache.lucene.index.IndexWriter.doFlush > (IndexWriter.java:2497) > at org.apache.lucene.index.IndexWriter.flush > (IndexWriter.java:2397) > at org.apache.lucene.index.IndexWriter.closeInternal > (IndexWriter.java:1204) > at org.apache.lucene.index.IndexWriter.close > (IndexWriter.java:1178) > at org.apache.lucene.index.IndexWriter.close > (IndexWriter.java:1153) > > Where I can find CheckIndex.tool ? > > Sergey Kabashnyuk > >> >> 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 this new assert is detecting. >> >> Mike >> >> Sergey Kabashnyuk wrote: >> >>> 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 >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: java-user-unsubscribe@... >>> For additional commands, e-mail: java-user-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> > > > > -- > Отправлено M2, революционной > почтовой программой Opera: http://www.opera.com/ > mail/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by Sergey Kabashnyuk-3
::
Rate this Message:
On Fri, 15 Feb 2008 16:31:07 +0200, Michael McCandless
<lucene@...> 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 instead of Exceptions. Why it's not very informative? > > 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 >> 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.java:1985) >> at org.apache.lucene.index.DocumentsWriter.flush >> (DocumentsWriter.java:539) >> at org.apache.lucene.index.IndexWriter.doFlush >> (IndexWriter.java:2497) >> at org.apache.lucene.index.IndexWriter.flush >> (IndexWriter.java:2397) >> at org.apache.lucene.index.IndexWriter.closeInternal >> (IndexWriter.java:1204) >> at org.apache.lucene.index.IndexWriter.close >> (IndexWriter.java:1178) >> at org.apache.lucene.index.IndexWriter.close >> (IndexWriter.java:1153) >> >> Where I can find CheckIndex.tool ? >> >> Sergey Kabashnyuk >> >>> >>> 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 this new assert is >>> detecting. >>> >>> Mike >>> >>> Sergey Kabashnyuk wrote: >>> >>>> 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 >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: java-user-unsubscribe@... >>>> For additional commands, e-mail: java-user-help@... >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: java-user-unsubscribe@... >>> For additional commands, e-mail: java-user-help@... >>> >> >> >> >> --Отправлено M2, революционной почтовой программой Opera: >> http://www.opera.com/mail/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > -- Отправлено M2, революционной почтовой программой Opera: http://www.opera.com/mail/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
Sergey Kabashnyuk wrote: > On Fri, 15 Feb 2008 16:31:07 +0200, Michael McCandless > <lucene@...> 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. Can you provide more details on how you're creating your documents? Are you using threads? (Or if possible post the code that's creating the documents?). > I have another question. > I see you use asserts in code 2.3.0 instead of Exceptions. Why it's > not very informative? Well, asserts are meant to catch bugs, whereas exceptions are meant to catch "expected" errors. But, you're right, it would be nice if the asserts included more details about the particular values that caused problems. I'll add that for this... Mike --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by fanfy
::
Rate this Message:
I'm also having a similar problem. Can you help me solve it? I'm only beginning to use lucene. This is the stack trace from a simple test that adds a document in the repository. I just created the jackrabbit repository so mine is not an upgrade from 2.2 to 2.3 problem. Anyway can you help me with some hints?
The tests are running under a nightly building server using jdk6 and maven2. Thank you. Caused by: java.lang.AssertionError: Terms are out of order: field=_:PROPERTIES (number 4) lastField=_:PROPERTIES (number 4) text=3:autoCreated lastText=3:autoCreated at org.apache.lucene.index.TermInfosWriter.add(TermInfosWriter.java:154) at org.apache.lucene.index.DocumentsWriter.appendPostings(DocumentsWriter.java:2316) at org.apache.lucene.index.DocumentsWriter.writeSegment(DocumentsWriter.java:2011) at org.apache.lucene.index.DocumentsWriter.flush(DocumentsWriter.java:548) at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:2497) at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:2397) at org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:1204) at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1178) at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1153) at org.apache.jackrabbit.core.query.lucene.AbstractIndex.commit(AbstractIndex.java:326) at org.apache.jackrabbit.core.query.lucene.VolatileIndex.commit(VolatileIndex.java:139) at org.apache.jackrabbit.core.query.lucene.PersistentIndex.copyIndex(PersistentIndex.java:121) at org.apache.jackrabbit.core.query.lucene.MultiIndex$VolatileCommit.execute(MultiIndex.java:1911) at org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog(MultiIndex.java:936) at org.apache.jackrabbit.core.query.lucene.MultiIndex.commitVolatileIndex(MultiIndex.java:986) at org.apache.jackrabbit.core.query.lucene.MultiIndex.flush(MultiIndex.java:868) at org.apache.jackrabbit.core.query.lucene.MultiIndex.close(MultiIndex.java:760) at org.apache.jackrabbit.core.query.lucene.SearchIndex.close(SearchIndex.java:630) at org.apache.jackrabbit.core.SearchManager.shutdownQueryHandler(SearchManager.java:588) at org.apache.jackrabbit.core.SearchManager.close(SearchManager.java:264) at org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.java:987) at org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java:948) at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:348) at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:557) at org.springmodules.jcr.jackrabbit.RepositoryFactoryBean.createRepository(RepositoryFactoryBean.java:57) at org.springmodules.jcr.RepositoryFactoryBean.afterPropertiesSet(RepositoryFactoryBean.java:57) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1333) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1299) ... 75 more
|
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
Which version of Jackrabbit are you using? Can you post the code of the simple test? Is it only adding a single document? Mike fanfy wrote: > > I'm also having a similar problem. Can you help me solve it? I'm only > beginning to use lucene. This is the stack trace from a simple test > that > adds a document in the repository. I just created the jackrabbit > repository > so mine is not an upgrade from 2.2 to 2.3 problem. Anyway can you > help me > with some hints? > The tests are running under a nightly building server using jdk6 > and maven2. > Thank you. > > Caused by: java.lang.AssertionError: Terms are out of order: > field=_:PROPERTIES (number 4) lastField=_:PROPERTIES (number 4) > text=3:autoCreated lastText=3:autoCreated > at org.apache.lucene.index.TermInfosWriter.add > (TermInfosWriter.java:154) > at > org.apache.lucene.index.DocumentsWriter.appendPostings > (DocumentsWriter.java:2316) > at > org.apache.lucene.index.DocumentsWriter.writeSegment > (DocumentsWriter.java:2011) > at org.apache.lucene.index.DocumentsWriter.flush > (DocumentsWriter.java:548) > at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:2497) > at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:2397) > at org.apache.lucene.index.IndexWriter.closeInternal > (IndexWriter.java:1204) > at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1178) > at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1153) > at > org.apache.jackrabbit.core.query.lucene.AbstractIndex.commit > (AbstractIndex.java:326) > at > org.apache.jackrabbit.core.query.lucene.VolatileIndex.commit > (VolatileIndex.java:139) > at > org.apache.jackrabbit.core.query.lucene.PersistentIndex.copyIndex > (PersistentIndex.java:121) > at > org.apache.jackrabbit.core.query.lucene.MultiIndex > $VolatileCommit.execute(MultiIndex.java:1911) > at > org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog > (MultiIndex.java:936) > at > org.apache.jackrabbit.core.query.lucene.MultiIndex.commitVolatileIndex > (MultiIndex.java:986) > at > org.apache.jackrabbit.core.query.lucene.MultiIndex.flush > (MultiIndex.java:868) > at > org.apache.jackrabbit.core.query.lucene.MultiIndex.close > (MultiIndex.java:760) > at > org.apache.jackrabbit.core.query.lucene.SearchIndex.close > (SearchIndex.java:630) > at > org.apache.jackrabbit.core.SearchManager.shutdownQueryHandler > (SearchManager.java:588) > at org.apache.jackrabbit.core.SearchManager.close > (SearchManager.java:264) > at > org.apache.jackrabbit.core.RepositoryImpl.doShutdown > (RepositoryImpl.java:987) > at > org.apache.jackrabbit.core.RepositoryImpl.shutdown > (RepositoryImpl.java:948) > at > org.apache.jackrabbit.core.RepositoryImpl.<init> > (RepositoryImpl.java:348) > at > org.apache.jackrabbit.core.RepositoryImpl.create > (RepositoryImpl.java:557) > at > org.springmodules.jcr.jackrabbit.RepositoryFactoryBean.createRepositor > y(RepositoryFactoryBean.java:57) > at > org.springmodules.jcr.RepositoryFactoryBean.afterPropertiesSet > (RepositoryFactoryBean.java:57) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanF > actory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1333) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanF > actory.initializeBean(AbstractAutowireCapableBeanFactory.java:1299) > ... 75 more > > > > Sergey Kabashnyuk-3 wrote: >> >> 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 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> >> >> > > -- > 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. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by fanfy
::
Rate this Message:
I'm using jackrabbit 1.4.2. The error doesn't appear all the time but when it does the solution is to delete the repository. The test is:
@Test public void addDocument() { documentService.importFile("Ana", "doc", new byte[200]); } documentService: public void importFile(final String name, final String contentType, final byte[] content) { jcrTemplate.execute(new JcrCallback() { public Object doInJcr(Session session) throws IOException, RepositoryException { Node rootNode = session.getRootNode(); Node fileNode = rootNode.addNode(name, "nt:file"); fileNode.addMixin("mix:referenceable"); Node resNode = fileNode.addNode("jcr:content", "nt:resource"); resNode.setProperty("jcr:data", new BinaryValue(content)); resNode.setProperty("jcr:mimeType", contentType); resNode.setProperty("jcr:lastModified", Calendar.getInstance()); session.save(); return resNode; } }); }
|
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
But, Jackrabbit 1.4.2 was released only yesterday, I think? Also, I think it's based on Lucene 2.2 not 2.3, yet your exception below is a 2.3 exception. Is it possible you're actually using a trunk build of Jackrabbit? Mike fanfy wrote: > > I'm using jackrabbit 1.4.2. The error doesn't appear all the time > but when it > does the solution is to delete the repository. The test is: > > @Test > public void addDocument() > { > documentService.importFile("Ana", "doc", new byte[200]); > } > > documentService: > public void importFile(final String name, final String > contentType, > final byte[] content) { > jcrTemplate.execute(new JcrCallback() { > > public Object doInJcr(Session session) throws IOException, > RepositoryException { > Node rootNode = session.getRootNode(); > Node fileNode = rootNode.addNode(name, "nt:file"); > fileNode.addMixin("mix:referenceable"); > Node resNode = fileNode.addNode("jcr:content", "nt:resource"); > > resNode.setProperty("jcr:data", new BinaryValue(content)); > resNode.setProperty("jcr:mimeType", contentType); > resNode.setProperty("jcr:lastModified", Calendar.getInstance()); > session.save(); > return resNode; > } > }); > } > > > Michael McCandless-2 wrote: >> >> >> Which version of Jackrabbit are you using? >> >> Can you post the code of the simple test? Is it only adding a single >> document? >> >> Mike >> >> fanfy wrote: >>> >>> I'm also having a similar problem. Can you help me solve it? I'm >>> only >>> beginning to use lucene. This is the stack trace from a simple test >>> that >>> adds a document in the repository. I just created the jackrabbit >>> repository >>> so mine is not an upgrade from 2.2 to 2.3 problem. Anyway can you >>> help me >>> with some hints? >>> The tests are running under a nightly building server using jdk6 >>> and maven2. >>> Thank you. >>> >>> Caused by: java.lang.AssertionError: Terms are out of order: >>> field=_:PROPERTIES (number 4) lastField=_:PROPERTIES (number 4) >>> text=3:autoCreated lastText=3:autoCreated >>> at org.apache.lucene.index.TermInfosWriter.add >>> (TermInfosWriter.java:154) >>> at >>> org.apache.lucene.index.DocumentsWriter.appendPostings >>> (DocumentsWriter.java:2316) >>> at >>> org.apache.lucene.index.DocumentsWriter.writeSegment >>> (DocumentsWriter.java:2011) >>> at org.apache.lucene.index.DocumentsWriter.flush >>> (DocumentsWriter.java:548) >>> at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java: >>> 2497) >>> at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:2397) >>> at org.apache.lucene.index.IndexWriter.closeInternal >>> (IndexWriter.java:1204) >>> at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1178) >>> at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1153) >>> at >>> org.apache.jackrabbit.core.query.lucene.AbstractIndex.commit >>> (AbstractIndex.java:326) >>> at >>> org.apache.jackrabbit.core.query.lucene.VolatileIndex.commit >>> (VolatileIndex.java:139) >>> at >>> org.apache.jackrabbit.core.query.lucene.PersistentIndex.copyIndex >>> (PersistentIndex.java:121) >>> at >>> org.apache.jackrabbit.core.query.lucene.MultiIndex >>> $VolatileCommit.execute(MultiIndex.java:1911) >>> at >>> org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog >>> (MultiIndex.java:936) >>> at >>> org.apache.jackrabbit.core.query.lucene.MultiIndex.commitVolatileInd >>> ex >>> (MultiIndex.java:986) >>> at >>> org.apache.jackrabbit.core.query.lucene.MultiIndex.flush >>> (MultiIndex.java:868) >>> at >>> org.apache.jackrabbit.core.query.lucene.MultiIndex.close >>> (MultiIndex.java:760) >>> at >>> org.apache.jackrabbit.core.query.lucene.SearchIndex.close >>> (SearchIndex.java:630) >>> at >>> org.apache.jackrabbit.core.SearchManager.shutdownQueryHandler >>> (SearchManager.java:588) >>> at org.apache.jackrabbit.core.SearchManager.close >>> (SearchManager.java:264) >>> at >>> org.apache.jackrabbit.core.RepositoryImpl.doShutdown >>> (RepositoryImpl.java:987) >>> at >>> org.apache.jackrabbit.core.RepositoryImpl.shutdown >>> (RepositoryImpl.java:948) >>> at >>> org.apache.jackrabbit.core.RepositoryImpl.<init> >>> (RepositoryImpl.java:348) >>> at >>> org.apache.jackrabbit.core.RepositoryImpl.create >>> (RepositoryImpl.java:557) >>> at >>> org.springmodules.jcr.jackrabbit.RepositoryFactoryBean.createReposit >>> or >>> y(RepositoryFactoryBean.java:57) >>> at >>> org.springmodules.jcr.RepositoryFactoryBean.afterPropertiesSet >>> (RepositoryFactoryBean.java:57) >>> at >>> org.springframework.beans.factory.support.AbstractAutowireCapableBea >>> nF >>> actory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java: >>> 1333) >>> at >>> org.springframework.beans.factory.support.AbstractAutowireCapableBea >>> nF >>> actory.initializeBean(AbstractAutowireCapableBeanFactory.java:1299) >>> ... 75 more >>> >>> >>> >>> Sergey Kabashnyuk-3 wrote: >>>> >>>> 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 >>>> >>>> ------------------------------------------------------------------- >>>> -- >>>> To unsubscribe, e-mail: java-user-unsubscribe@... >>>> For additional commands, e-mail: java-user-help@... >>>> >>>> >>>> >>> >>> -- >>> 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. >>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: java-user-unsubscribe@... >>> For additional commands, e-mail: java-user-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/from--2.2.0- > to-2.3.0-tp15501449p16354912.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
|
|
Re: from 2.2.0 to 2.3.0
by fanfy
::
Rate this Message:
Sorry, my mistake, it was 1.4.1 with lucene 2.3.1. Today I upgraded to 1.4.2 and in the same time I downgraded the lucene to 2.2.0 and now it works (don't know for how long). So, do you think that this error is related to jackrabbit being developed with an older lucene version? I'll use the 2.2.0 version and hope the error doesn't appear. Thank you for the quick reply.
|
|
|
Re: from 2.2.0 to 2.3.0
by Michael McCandless-2
::
Rate this Message:
OK, yes, I'm guessing this explains your issue: https://issues.apache.org/jira/browse/JCR-1363 I think Jackrabbit doesn't yet work with Lucene 2.3. But please post back if you see issues with Lucene 2.2! Mike fanfy wrote: > > Sorry, my mistake, it was 1.4.1 with lucene 2.3.1. Today I upgraded > to 1.4.2 > and in the same time I downgraded the lucene to 2.2.0 and now it works > (don't know for how long). So, do you think that this error is > related to > jackrabbit being developed with an older lucene version? I'll use > the 2.2.0 > version and hope the error doesn't appear. Thank you for the quick > reply. > > > Michael McCandless-2 wrote: >> >> >> But, Jackrabbit 1.4.2 was released only yesterday, I think? Also, I >> think it's based on Lucene 2.2 not 2.3, yet your exception below is a >> 2.3 exception. >> >> Is it possible you're actually using a trunk build of Jackrabbit? >> >> Mike >> >> fanfy wrote: >>> >>> I'm using jackrabbit 1.4.2. The error doesn't appear all the time >>> but when it >>> does the solution is to delete the repository. The test is: >>> >>> @Test >>> public void addDocument() >>> { >>> documentService.importFile("Ana", "doc", new byte[200]); >>> } >>> >>> documentService: >>> public void importFile(final String name, final String >>> contentType, >>> final byte[] content) { >>> jcrTemplate.execute(new JcrCallback() { >>> >>> public Object doInJcr(Session session) throws IOException, >>> RepositoryException { >>> Node rootNode = session.getRootNode(); >>> Node fileNode = rootNode.addNode(name, "nt:file"); >>> fileNode.addMixin("mix:referenceable"); >>> Node resNode = fileNode.addNode("jcr:content", "nt:resource"); >>> >>> resNode.setProperty("jcr:data", new BinaryValue(content)); >>> resNode.setProperty("jcr:mimeType", contentType); >>> resNode.setProperty("jcr:lastModified", Calendar.getInstance()); >>> session.save(); >>> return resNode; >>> } >>> }); >>> } >>> >>> >>> Michael McCandless-2 wrote: >>>> >>>> >>>> Which version of Jackrabbit are you using? >>>> >>>> Can you post the code of the simple test? Is it only adding a >>>> single >>>> document? >>>> >>>> Mike >>>> >>>> fanfy wrote: >>>>> >>>>> I'm also having a similar problem. Can you help me solve it? I'm >>>>> only >>>>> beginning to use lucene. This is the stack trace from a simple >>>>> test >>>>> that >>>>> adds a document in the repository. I just created the jackrabbit >>>>> repository >>>>> so mine is not an upgrade from 2.2 to 2.3 problem. Anyway can you >>>>> help me >>>>> with some hints? >>>>> The tests are running under a nightly building server using jdk6 >>>>> and maven2. >>>>> Thank you. >>>>> >>>>> Caused by: java.lang.AssertionError: Terms are out of order: >>>>> field=_:PROPERTIES (number 4) lastField=_:PROPERTIES (number 4) >>>>> text=3:autoCreated lastText=3:autoCreated >>>>> at org.apache.lucene.index.TermInfosWriter.add >>>>> (TermInfosWriter.java:154) >>>>> at >>>>> org.apache.lucene.index.DocumentsWriter.appendPostings >>>>> (DocumentsWriter.java:2316) >>>>> at >>>>> org.apache.lucene.index.DocumentsWriter.writeSegment >>>>> (DocumentsWriter.java:2011) >>>>> at org.apache.lucene.index.DocumentsWriter.flush >>>>> (DocumentsWriter.java:548) >>>>> at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java: >>>>> 2497) >>>>> at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java: >>>>> 2397) >>>>> at org.apache.lucene.index.IndexWriter.closeInternal >>>>> (IndexWriter.java:1204) >>>>> at org.apache.lucene.index.IndexWriter.close(IndexWriter.java: >>>>> 1178) >>>>> at org.apache.lucene.index.IndexWriter.close(IndexWriter.java: >>>>> 1153) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.AbstractIndex.commit >>>>> (AbstractIndex.java:326) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.VolatileIndex.commit >>>>> (VolatileIndex.java:139) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.PersistentIndex.copyIndex >>>>> (PersistentIndex.java:121) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.MultiIndex >>>>> $VolatileCommit.execute(MultiIndex.java:1911) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog >>>>> (MultiIndex.java:936) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.MultiIndex.commitVolatileI >>>>> nd >>>>> ex >>>>> (MultiIndex.java:986) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.MultiIndex.flush >>>>> (MultiIndex.java:868) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.MultiIndex.close >>>>> (MultiIndex.java:760) >>>>> at >>>>> org.apache.jackrabbit.core.query.lucene.SearchIndex.close >>>>> (SearchIndex.java:630) >>>>> at >>>>> org.apache.jackrabbit.core.SearchManager.shutdownQueryHandler >>>>> (SearchManager.java:588) >>>>> at org.apache.jackrabbit.core.SearchManager.close >>>>> (SearchManager.java:264) >>>>> at >>>>> org.apache.jackrabbit.core.RepositoryImpl.doShutdown >>>>> (RepositoryImpl.java:987) >>>>> at >>>>> org.apache.jackrabbit.core.RepositoryImpl.shutdown >>>>> (RepositoryImpl.java:948) >>>>> at >>>>> org.apache.jackrabbit.core.RepositoryImpl.<init> >>>>> (RepositoryImpl.java:348) >>>>> at >>>>> org.apache.jackrabbit.core.RepositoryImpl.create >>>>> (RepositoryImpl.java:557) >>>>> at >>>>> org.springmodules.jcr.jackrabbit.RepositoryFactoryBean.createRepos >>>>> it >>>>> or >>>>> y(RepositoryFactoryBean.java:57) >>>>> at >>>>> org.springmodules.jcr.RepositoryFactoryBean.afterPropertiesSet >>>>> (RepositoryFactoryBean.java:57) >>>>> at >>>>> org.springframework.beans.factory.support.AbstractAutowireCapableB >>>>> ea >>>>> nF >>>>> actory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java: >>>>> 1333) >>>>> at >>>>> org.springframework.beans.factory.support.AbstractAutowireCapableB >>>>> ea >>>>> nF >>>>> actory.initializeBean(AbstractAutowireCapableBeanFactory.java: >>>>> 1299) >>>>> ... 75 more >>>>> >>>>> >>>>> >>>>> Sergey Kabashnyuk-3 wrote: >>>>>> >>>>>> 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 >>>>>> >>>>>> ----------------------------------------------------------------- >>>>>> -- >>>>>> -- >>>>>> To unsubscribe, e-mail: java-user-unsubscribe@... >>>>>> For additional commands, e-mail: java-user-help@... >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> 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. >>>>> >>>>> >>>>> ------------------------------------------------------------------ >>>>> -- >>>>> - >>>>> To unsubscribe, e-mail: java-user-unsubscribe@... >>>>> For additional commands, e-mail: java-user-help@... >>>>> >>>> >>>> >>>> ------------------------------------------------------------------- >>>> -- >>>> To unsubscribe, e-mail: java-user-unsubscribe@... >>>> For additional commands, e-mail: java-user-help@... >>>> >>>> >>>> >>> >>> -- >>> View this message in context: http://www.nabble.com/from--2.2.0- >>> to-2.3.0-tp15501449p16354912.html >>> Sent from the Lucene - Java Users mailing list archive at >>> Nabble.com. >>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: java-user-unsubscribe@... >>> For additional commands, e-mail: java-user-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@... >> For additional commands, e-mail: java-user-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/from--2.2.0- > to-2.3.0-tp15501449p16361119.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@... > For additional commands, e-mail: java-user-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@... For additional commands, e-mail: java-user-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
