[jira] Resolved: (LUCENE-1118) core analyzers should not produce tokens > N (100?) characters in length

[ https://issues.apache.org/jira/browse/LUCENE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1118. Resolution: Fixed > core analyzers should not produce tokens > N (100?) characters

[jira] Resolved: (LUCENE-1119) Optimize TermInfosWriter.add

[ https://issues.apache.org/jira/browse/LUCENE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1119. Resolution: Fixed > Optimize TermInfosWriter.add > >

Build failed in Hudson: Lucene-Nightly #330

See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/330/changes -- [...truncated 895 lines...] A contrib/db/bdb/src/java/org/apache/lucene/store/db AUcontrib/db/bdb/src/java/org/apache/lucene/store/db/File.java AUcontrib

Lucene lock file created

Hi all... I am having a problem with lucene lock files. Apache Tomcat is my server. My search functionality was very well working. but some how a lock file was created in /opt/apache.../temp directory. after that indexing failed. can anyone tell me why and when this lock file was created. It star

Too ambitious : but wanting to know the exact procedure.

Hi all. I have been going through a lot of Lucene tutorials; but everywhere what I find is just how to use Lucene classes (IndexReader, IndexSearcher, Analyzer, Field, Doc . list goes on). Everything fine so far, but I still feel that all these "cook-book" rules can be better understood