lucene RAMDirectory org.apache.lucene.index.IndexNotFoundException

最新推荐文章于 2024-08-30 19:34:39 发布

原创最新推荐文章于 2024-08-30 19:34:39 发布 · 3.1k 阅读

0 ·

CC 4.0 BY-SA版权

lucene 同时被 3 个专栏收录

2 篇文章

订阅专栏

解决的问题

1 篇文章

订阅专栏

excption

1 篇文章

订阅专栏

本文介绍了一个在使用Lucene进行内存索引操作时遇到的IndexNotFoundException异常，并详细展示了异常堆栈跟踪信息。通过分析发现，问题在于使用了两个不同的RAMDirectory实例，最后给出了通过单例模式确保RAMDirectory唯一性的解决方案。

lucene RAMDirectory org.apache.lucene.index.IndexNotFoundException

今天在使用lucene的时候遇见这个异常:

org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.RAMDirectory@149b290 lockFactory=org.apache.lucene.store.SingleInstanceLockFactory@16a38b5: files: [] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:712) at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:75) at org.apache.lucene.index.IndexReader.open(IndexReader.java:462) at org.apache.lucene.index.IndexReader.open(IndexReader.java:322) at org.apache.lucene.search.IndexSearcher.<init>(IndexSearcher.java:93) at service.IndexServiceImpl.searchByboolean(IndexServiceImpl.java:136) at service.IndexServiceImpl.byBooleanQueryFromM(IndexServiceImpl.java:107) at test.IndexTest.testIndexCreateImMAndSearch(IndexTest.java:116) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

其实问题很简单.... (但是百度,谷歌却没定点痕迹告诉我怎么做...)

这里是创建内存索引的地方:

writer = new IndexWriter(new RAMDirectory (), indexConfig);

实例化一个IndexWriter.. 其中的RAMDirectory 是新实例化的:

好.在读取内存索引的语句是:

searcher = new IndexSearcher( new  RAMDirectory());

注意:这里产生了两个 RAMDirectory ..就是这里出现的问题...

解决方法很简单,用单例模式,保证是同一个引用就好:

	ramDir = IndexFactroy.getRAMDirtoryInstance();
				writer = new IndexWriter(ramDir , indexConfig);