From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] U (unread) search is off
Date: Sun, 13 Sep 2009 20:31:23 -0400 [thread overview]
Message-ID: <1252878152-sup-9190@zyrg.net> (raw)
In-Reply-To: <1252773806-sup-11@masanjin.net>
Excerpts from William Morgan's message of Sat Sep 12 12:47:14 -0400 2009:
> Reformatted excerpts from Rich Lane's message of 2009-09-10:
> > I thought it was, but it turns out that unless you explicitly add AND
> > operators Xapian will OR terms over the same field such that
> > "label:foo label:bar" gives you the union instead of the intersection.
>
> Ok. I only ask because I'm considering how to present the Xapian index
> option in 0.9---the options are to not say anything about it, to force
> everyone to switch to it, or anywhere in between.
Yeah, we do need the query behavior to be reasonable before advertising
the Xapian index. What's your timeline on 0.9?
> > We could fix this by patching Xapian to make this behavior
> > configurable, or we could come up with an index-agnostic simple query
> > language that doesn't support boolean operators.
>
> The former sounds easier to me. Especially since it seems like this is
> something Xapian should have...
Agreed that Xapian should have this, and I'll probably implement it. We
still need to support people using older Xapian versions though. Whether
this means a log message telling them to use explicit ANDs in their
query, or automatically transforming simple-enough queries into what we
think they actually want, I don't know. I'll also need to add a
workaround for the earlier Xapian bug before this index gets wider
usage.
As far as which index to make the default, Ferret has the advantage of
being installable as a gem dependency. I think this ease of installation
is important enough to block Xapian for now, unless someone can create a
Xapian gem. There's been interest in this before:
http://article.gmane.org/gmane.comp.search.xapian.devel/1408/
next prev parent reply other threads:[~2009-09-14 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 13:54 Ben Walton
2009-09-10 11:22 ` Ingmar Vanhassel
2009-09-10 13:59 ` William Morgan
2009-09-10 14:04 ` Ben Walton
2009-09-10 16:17 ` Rich Lane
2009-09-10 17:13 ` Ben Walton
2009-09-10 14:08 ` Ingmar Vanhassel
2009-09-10 16:16 ` Rich Lane
2009-09-12 16:47 ` William Morgan
2009-09-14 0:31 ` Rich Lane [this message]
2009-09-15 7:18 ` Olly Betts
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=1252878152-sup-9190@zyrg.net \
--to=rlane@club.cc.cmu.edu \
/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