From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] bug: reproducable Sup crash, ferret-less rewrite?
Date: Sun, 02 Nov 2008 10:30:54 -0800 [thread overview]
Message-ID: <1225650088-sup-7423@entry> (raw)
In-Reply-To: <J4OdBBA7.1225577624.9061510.tpo2@192.168.3.7>
Reformatted excerpts from Tomas Pospisek ML's message of 2008-11-01:
> - has anybody tried to swap Ferret with any other indexer [also in
> [1]]?
Not AFAIK. There are a couple indexing options with Ruby bindings:
Sphinx, Xapian, Solr, and HyperEstraier, off the top of my head. When I
last looked, they all had their problems: Sphinx requires a daemon, is
overly tied to databases, and has no incremental indexing, Xapian is
confusing and doesn't seem to support document fields, Solr is Java,
HyperEstraier doesn't seem to have anyone using it, etc.
> - has anybody tried to fix the index corruption / ferret crash bug [2]?
I'd love for someone to do this! Ferret has the best API and document
model, by far, of any of the alternatives.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-11-02 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 23:52 Tomas Pospisek ML
2008-11-01 3:16 ` Christopher Warrington
2008-11-01 22:13 ` Tomas Pospisek ML
2008-11-02 18:30 ` William Morgan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1225650088-sup-7423@entry \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox