Hi!
Beware that Lucene API is evolving (version 2.4) with basic classes like
Hits becoming deprecated (supressed in future 3.0).
Stored data structure has also changed with automatic conversion taking
place at first use (you must also upgrade your Luke:
http://www.getopt.org/luke/)
Even if they did not changed the major version number...
This seems to be for (future?) performance improvements in Lucene.
But, seriously, Lucene is already astonishingly performant.
Some caching of search hits number can be useful if a search is often
repeated to help users within an Auto-complete (this cache must be
thrown away when Lucene IndexWriter is called but, in a Wiki, pages are
much more often read than writen).
Have a nice w.e.!
Christophe
Harry Metske (JIRA) a écrit :
[ https://issues.apache.org/jira/browse/JSPWIKI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673598#action_12673598 ]
Harry Metske commented on JSPWIKI-498:
--------------------------------------
And again, JUnit tests is also very important.
JSPWiki currently has 1049 JUnit tests, and this really helps preventing us breaking things.
This has been a serious investment and we profit from that every day. We want
to keep relying on it.
Performance Issues with Lucene Index
------------------------------------
Key: JSPWIKI-498
URL: https://issues.apache.org/jira/browse/JSPWIKI-498
Project: JSPWiki
Issue Type: Bug
Components: Default template
Affects Versions: 2.8.1
Environment: Win 2003 on XEN-Server, 3 GB RAM, 4 x Intel Xeon 2Ghz
Reporter: Kurt Stein
Attachments: patch_lucene_search.txt, patch_lucene_search_2.txt,
screenshot-1.jpg
Our Wiki-Luceneindex has swollen to 33 MB and if someone searches words like
"find" he gets about 500 results. Only problem is, it takes about 30 seconds to
complete the search.
I have looked a bit into the problem and there is something strange to me. JSPWiki searches twice every query.
Once in search.jsp and afterwards in AjaxSearch.jsp.
The filteredList from search.jsp is written to the pagecontext but this
information is never read within the AjaxSearch.jsp. Thus AjaxSearch.jsp makes
a second search.
