aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/lucene_search_engine.mdwn
diff options
context:
space:
mode:
authorhttps://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web>2012-11-30 00:40:43 -0400
committeradmin <admin@branchable.com>2012-11-30 00:40:43 -0400
commit29f111c47c2bcae941bb3d604a95c64b7c374255 (patch)
treec1b9e64101774b3ff5c3b250cab9da32fcf292bd /doc/todo/lucene_search_engine.mdwn
parent537579315af13e2408af585af15bd5bc0b209853 (diff)
downloadikiwiki-29f111c47c2bcae941bb3d604a95c64b7c374255.tar
ikiwiki-29f111c47c2bcae941bb3d604a95c64b7c374255.tar.gz
why not try lucene too?
Diffstat (limited to 'doc/todo/lucene_search_engine.mdwn')
-rw-r--r--doc/todo/lucene_search_engine.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/todo/lucene_search_engine.mdwn b/doc/todo/lucene_search_engine.mdwn
new file mode 100644
index 000000000..694c81c4c
--- /dev/null
+++ b/doc/todo/lucene_search_engine.mdwn
@@ -0,0 +1 @@
+There are [some issue](http://www.branchable.com/bugs/Exception:_Cannot_open_tables_at_consistent_revisions_at___47__usr__47__lib__47__perl5__47__Search__47__Xapian__47__WritableDatabase.pm_line_41./#comment-c159ea3f9be35fcd9ed0eeedb162e816) with the current search engine. Sometimes the database gets corrupted and it's not very good at weighting say, the title against the content. In [[different_search_engine]], there was the idea of using Lucene - is there any reason why we should have both, or at least let lucene live in contrib?