LuceneModule

Lucene fails to create an index on first run, fails even when tried manually thereafter

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.0
  • Component/s: None
  • Description:
    Hide
    The Lucene module fails to create an index when first run. Reloading the module and/or manually starting full indexes have no effect since it can not seem to find its 'lastIndexed.properties' file:

    2009-12-02 15:25:00,469 DEB mmbase.module.lucene.Indexer loadLastFullIndexTimes.202 - java.io.FileNotFoundException: /apache-tomcat-5.5.26/webapps/ROOT/WEB-INF/data/lucene/lastIndexed.properties (No such file or directory)
    Show
    The Lucene module fails to create an index when first run. Reloading the module and/or manually starting full indexes have no effect since it can not seem to find its 'lastIndexed.properties' file: 2009-12-02 15:25:00,469 DEB mmbase.module.lucene.Indexer loadLastFullIndexTimes.202 - java.io.FileNotFoundException: /apache-tomcat-5.5.26/webapps/ROOT/WEB-INF/data/lucene/lastIndexed.properties (No such file or directory)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
André van Toly added a comment - 2010-01-11 16:56
Moved this.fullIndex() when no full index has been run yet to the end of the constructor of Indexer, this seems to fix it.
Show
André van Toly added a comment - 2010-01-11 16:56 Moved this.fullIndex() when no full index has been run yet to the end of the constructor of Indexer, this seems to fix it.
Hide
Permalink
Michiel Meeuwissen added a comment - 2010-01-12 10:18
I think it would be nicer to not do it in the constructor, but leave it to the scheduler. The complete configuration can be reviewed then immediately. Full-indexing can be cancelled then too. Perhaps it should also be combined with the existing option 'fullindexatstartupt, perhaps with an extra value 'whenneeded' or so.
Show
Michiel Meeuwissen added a comment - 2010-01-12 10:18 I think it would be nicer to not do it in the constructor, but leave it to the scheduler. The complete configuration can be reviewed then immediately. Full-indexing can be cancelled then too. Perhaps it should also be combined with the existing option 'fullindexatstartupt, perhaps with an extra value 'whenneeded' or so.
Hide
Permalink
André van Toly added a comment - 2012-06-21 16:09
Fixed, I believe.
Show
André van Toly added a comment - 2012-06-21 16:09 Fixed, I believe.

People

Dates

  • Created:
    2009-12-02 15:28
    Updated:
    2012-06-21 16:09
    Resolved:
    2012-06-21 16:09
Atlassian JIRA (v4.1#519) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for MMBase Foundation. Try JIRA - bug tracking software for your team.