Hi, >From the logs I see that the index is being rebuild and fails before it is finished.This seems to be caused by a persisted single valued property of Calendar type without a value, which may be caused by the problem described in JCR-1996. The index building needs to be made more robust. Can you please create an issue for this? Thanks!
Ways to solve this: do you still have a backup of the search index? You may be able to re-use that one, but be aware that it might be out-of-sync with the persisted content. Another way is to patch the 1.5.5 jackrabbit-core with a null check around line 508 in the NodeIndexer class... I hope that helps. Best regards, Martijn On Tue, Dec 15, 2009 at 9:10 AM, Thomas Müller <[email protected]> wrote: > Hi, > > Maybe re-building the Lucene index will solve the problem. See also: > http://wiki.apache.org/jackrabbit/Search#Rebuilding_the_Index > > Regards, > Thomas > > > On Tue, Dec 15, 2009 at 3:53 AM, gaott <[email protected]> wrote: >> >> I try to build a repository including 7 million data(no binaries), now I've >> store 1.3m data, but I got an error, and then I can't start the repository. >> >> I set the log4j level to debug, and see that the calendar index of one node >> indexed failed when start the repository. >> >> I use jackrabbit-core-1.5.5. What can I do now? I don't wanna waste the 1.3m >> data... >> >> I upload the log for more information. >> >> thanks very much. >> http://n4.nabble.com/file/n964039/dmcs.log dmcs.log >> >> ----- >> the easier, the better:-) >> -- >> View this message in context: >> http://n4.nabble.com/start-repository-failed-caused-by-error-index-tp964039p964039.html >> Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >> >
