[jira] Resolved: (LUCENE-1199) NullPointerException in IndexModifier.close()
[ https://issues.apache.org/jira/browse/LUCENE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1199. Resolution: Fixed Fix Version/s: 2.4 OK I just committed a defensive check that indexReader != null before we close it. But note that IndexModifier is now deprecated and will be removed in 3.0. > NullPointerException in IndexModifier.close() > - > > Key: LUCENE-1199 > URL: https://issues.apache.org/jira/browse/LUCENE-1199 > Project: Lucene - Java > Issue Type: Bug > Components: Index >Affects Versions: 2.0.0, 2.3.1 >Reporter: James William Dumay > Fix For: 2.4 > > > We upgraded from Lucene 2.0.0. to 2.3.1 hoping this would resolve this issue. > http://jira.codehaus.org/browse/MRM-715 > Trace is as below for Lucene 2.3.1: > java.lang.NullPointerException > at org.apache.lucene.index.IndexModifier.close(IndexModifier.java:576) > at > org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.closeQuietly(LuceneRepositoryContentIndex.java:416) > at > org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.modifyRecord(LuceneRepositoryContentIndex.java:152) > at > org.apache.maven.archiva.consumers.lucene.IndexContentConsumer.processFile(IndexContentConsumer.java:169) > at > org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:51) > at > org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117) > at > org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) > at > org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:283) > at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:597) > at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:157) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:447) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:354) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189) > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > at > org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-1199) NullPointerException in IndexModifier.close()
[ https://issues.apache.org/jira/browse/LUCENE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574308#action_12574308 ] Brett Porter commented on LUCENE-1199: -- in my case there weren't any from Lucene - I came to the same conclusion and couldn't understand why this would be. The only other thought is if close() gets called twice but I couldn't see that in our code either. > NullPointerException in IndexModifier.close() > - > > Key: LUCENE-1199 > URL: https://issues.apache.org/jira/browse/LUCENE-1199 > Project: Lucene - Java > Issue Type: Bug > Components: Index >Affects Versions: 2.0.0, 2.3.1 >Reporter: James William Dumay > > We upgraded from Lucene 2.0.0. to 2.3.1 hoping this would resolve this issue. > http://jira.codehaus.org/browse/MRM-715 > Trace is as below for Lucene 2.3.1: > java.lang.NullPointerException > at org.apache.lucene.index.IndexModifier.close(IndexModifier.java:576) > at > org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.closeQuietly(LuceneRepositoryContentIndex.java:416) > at > org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.modifyRecord(LuceneRepositoryContentIndex.java:152) > at > org.apache.maven.archiva.consumers.lucene.IndexContentConsumer.processFile(IndexContentConsumer.java:169) > at > org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:51) > at > org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117) > at > org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) > at > org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:283) > at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:597) > at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:157) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:447) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:354) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189) > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > at > org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-1199) NullPointerException in IndexModifier.close()
[ https://issues.apache.org/jira/browse/LUCENE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574307#action_12574307 ] Michael McCandless commented on LUCENE-1199: Were there any prior exceptions before you hit this one? It's hard to see how IndexModifier could have both its indexReader & indexWriter null, unless it had hit an exception on re-opening one of them. > NullPointerException in IndexModifier.close() > - > > Key: LUCENE-1199 > URL: https://issues.apache.org/jira/browse/LUCENE-1199 > Project: Lucene - Java > Issue Type: Bug > Components: Index >Affects Versions: 2.0.0, 2.3.1 >Reporter: James William Dumay > > We upgraded from Lucene 2.0.0. to 2.3.1 hoping this would resolve this issue. > http://jira.codehaus.org/browse/MRM-715 > Trace is as below for Lucene 2.3.1: > java.lang.NullPointerException > at org.apache.lucene.index.IndexModifier.close(IndexModifier.java:576) > at > org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.closeQuietly(LuceneRepositoryContentIndex.java:416) > at > org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.modifyRecord(LuceneRepositoryContentIndex.java:152) > at > org.apache.maven.archiva.consumers.lucene.IndexContentConsumer.processFile(IndexContentConsumer.java:169) > at > org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:51) > at > org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117) > at > org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) > at > org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:283) > at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:597) > at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:157) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:447) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:354) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189) > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > at > org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (LUCENE-1198) Exception in DocumentsWriter.ThreadState.init leads to corruption
[ https://issues.apache.org/jira/browse/LUCENE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1198. Resolution: Fixed > Exception in DocumentsWriter.ThreadState.init leads to corruption > - > > Key: LUCENE-1198 > URL: https://issues.apache.org/jira/browse/LUCENE-1198 > Project: Lucene - Java > Issue Type: Bug > Components: Index >Affects Versions: 2.3 >Reporter: Michael McCandless >Assignee: Michael McCandless >Priority: Minor > Fix For: 2.4 > > Attachments: LUCENE-1198.patch > > > If an exception is hit in the init method, DocumentsWriter incorrectly > increments numDocsInRAM when in fact the document is not added. > Spinoff of this thread: > http://markmail.org/message/e76hgkgldxhakuaa > The root cause that led to the exception in init was actually due to > incorrect use of Lucene's APIs (one thread still modifying the > Document while IndexWriter.addDocument is adding it) but still we > should protect against any exceptions coming out of init. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (LUCENE-1199) NullPointerException in IndexModifier.close()
NullPointerException in IndexModifier.close() - Key: LUCENE-1199 URL: https://issues.apache.org/jira/browse/LUCENE-1199 Project: Lucene - Java Issue Type: Bug Components: Index Affects Versions: 2.3.1, 2.0.0 Reporter: James William Dumay We upgraded from Lucene 2.0.0. to 2.3.1 hoping this would resolve this issue. http://jira.codehaus.org/browse/MRM-715 Trace is as below for Lucene 2.3.1: java.lang.NullPointerException at org.apache.lucene.index.IndexModifier.close(IndexModifier.java:576) at org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.closeQuietly(LuceneRepositoryContentIndex.java:416) at org.apache.maven.archiva.indexer.lucene.LuceneRepositoryContentIndex.modifyRecord(LuceneRepositoryContentIndex.java:152) at org.apache.maven.archiva.consumers.lucene.IndexContentConsumer.processFile(IndexContentConsumer.java:169) at org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:51) at org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117) at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388) at org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:283) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:597) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:157) at org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:447) at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:354) at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189) at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) at org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: GSoC projects
FYI. Anyone have ideas for projects? Begin forwarded message: From: "Ryan McKinley" <[EMAIL PROTECTED]> Date: March 2, 2008 8:36:24 AM EST To: [EMAIL PROTECTED] Subject: Fwd: GSoC projects Reply-To: [EMAIL PROTECTED] Any concrete projects we should consider? -- Forwarded message -- From: Ross Gardler <[EMAIL PROTECTED]> Date: Feb 29, 2008 5:34 PM Subject: GSoC projects To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Google are running GSoC again this year. Discussion of GSoC events happens on [EMAIL PROTECTED] First point of business is to decide if you want to mentor a project this year and to ensure that your project is happy to host a GSoC student. More info on what it means to be a mentor in the ASF can be found at [1], it's a bit sparse on info but you can always ask on code- [EMAIL PROTECTED] (and don't forget to help fill up the wiki page) If you have a project idea then please add it to [2] The deadline for project proposals is March 12th Ross [1] http://wiki.apache.org/general/SummerOfCodeMentor [2] http://wiki.apache.org/general/SummerOfCode2008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (LUCENE-1190) a lexicon object for merging spellchecker and synonyms from stemming
hum, quote and question disappear. Le 2 mars 08 à 13:32, Mathieu Lecarme (JIRA) a écrit : [ https://issues.apache.org/jira/browse/LUCENE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574214 #action_12574214 ] Mathieu Lecarme commented on LUCENE-1190: - >> For example, I don't know what you mean by "Some Lucene features need a list of referring word". Do you mean "a list of associated words"? With a FuzzyQuery, for example, you iterate over Term in index, and looking for the nearest one. PrefixQuery or regular expression work in a similar way. If you say, fuzzy querying will never gives a word with different size of 1 (size+1 or size -1), you can restrict the list of candidates, and ngram index can help you more. Some token filter destroy the word. Stemmer for example. If you wont to search wide, stemmer can help you, but can't use PrefixQuery with stemmed word. So, you can stemme word in a lexicon and use it as a synonym. You index "dog" and look for "doggy", "dogs" and "dog". Lexicon can use static list of word, from hunspell index or wikipedia parsing, or words extracted from your index. >> Each meta is a Field what do you mean by that? Could you please give an example? for the word "Lucene" : word:lucene pop:42 anagram.anagram:celnu aphone.start:LS aphone.gram:LS aphone.gram:SN aphone.end:SN aphone.size:3 aphone.phonem:LSN ngram.start:lu ngram.gram:lu ngram.gram:uc ngram.gram:ce ngram.gram:en ngram.gram:ne ngram.end:ne ngram.size:6 stemmer.stem:lucen >> Hm, not sure I know what you mean. Are you saying that once you create a sufficiently large lexicon/dictionary/index, the number of new terms starts decreasing? (Heap's Law? http://en.wikipedia.org/wiki/Heaps'_law ) Yes. a lexicon object for merging spellchecker and synonyms from stemming Key: LUCENE-1190 URL: https://issues.apache.org/jira/browse/LUCENE-1190 Project: Lucene - Java Issue Type: New Feature Components: contrib/*, Search Affects Versions: 2.3 Reporter: Mathieu Lecarme Attachments: aphone+lexicon.patch, aphone+lexicon.patch Some Lucene features need a list of referring word. Spellchecking is the basic example, but synonyms is an other use. Other tools can be used smoothlier with a list of words, without disturbing the main index : stemming and other simplification of word (anagram, phonetic ...). For that, I suggest a Lexicon object, wich contains words (Term + frequency), wich can be built from Lucene Directory, or plain text files. Classical TokenFilter can be used with Lexicon (LowerCaseFilter and ISOLatin1AccentFilter should be the most useful). Lexicon uses a Lucene Directory, each Word is a Document, each meta is a Field (word, ngram, phonetic, fields, anagram, size ...). Above a minimum size, number of differents words used in an index can be considered as stable. So, a standard Lexicon (built from wikipedia by example) can be used. A similarTokenFilter is provided. A spellchecker will come soon. A fuzzySearch implementation, a neutral synonym TokenFilter can be done. Unused words can be remove on demand (lazy delete?) Any criticism or suggestions? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-1190) a lexicon object for merging spellchecker and synonyms from stemming
[ https://issues.apache.org/jira/browse/LUCENE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574214#action_12574214 ] Mathieu Lecarme commented on LUCENE-1190: - With a FuzzyQuery, for example, you iterate over Term in index, and looking for the nearest one. PrefixQuery or regular expression work in a similar way. If you say, fuzzy querying will never gives a word with different size of 1 (size+1 or size -1), you can restrict the list of candidates, and ngram index can help you more. Some token filter destroy the word. Stemmer for example. If you wont to search wide, stemmer can help you, but can't use PrefixQuery with stemmed word. So, you can stemme word in a lexicon and use it as a synonym. You index "dog" and look for "doggy", "dogs" and "dog". Lexicon can use static list of word, from hunspell index or wikipedia parsing, or words extracted from your index. for the word "Lucene" : word:lucene pop:42 anagram.anagram:celnu aphone.start:LS aphone.gram:LS aphone.gram:SN aphone.end:SN aphone.size:3 aphone.phonem:LSN ngram.start:lu ngram.gram:lu ngram.gram:uc ngram.gram:ce ngram.gram:en ngram.gram:ne ngram.end:ne ngram.size:6 stemmer.stem:lucen Yes. M. > a lexicon object for merging spellchecker and synonyms from stemming > > > Key: LUCENE-1190 > URL: https://issues.apache.org/jira/browse/LUCENE-1190 > Project: Lucene - Java > Issue Type: New Feature > Components: contrib/*, Search >Affects Versions: 2.3 >Reporter: Mathieu Lecarme > Attachments: aphone+lexicon.patch, aphone+lexicon.patch > > > Some Lucene features need a list of referring word. Spellchecking is the > basic example, but synonyms is an other use. Other tools can be used > smoothlier with a list of words, without disturbing the main index : stemming > and other simplification of word (anagram, phonetic ...). > For that, I suggest a Lexicon object, wich contains words (Term + frequency), > wich can be built from Lucene Directory, or plain text files. > Classical TokenFilter can be used with Lexicon (LowerCaseFilter and > ISOLatin1AccentFilter should be the most useful). > Lexicon uses a Lucene Directory, each Word is a Document, each meta is a > Field (word, ngram, phonetic, fields, anagram, size ...). > Above a minimum size, number of differents words used in an index can be > considered as stable. So, a standard Lexicon (built from wikipedia by > example) can be used. > A similarTokenFilter is provided. > A spellchecker will come soon. > A fuzzySearch implementation, a neutral synonym TokenFilter can be done. > Unused words can be remove on demand (lazy delete?) > Any criticism or suggestions? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
