From: Carl Worth <cworth@cworth.org>
To: Austin Clements <amdragon@gmail.com>,
	Mark Anderson <MarkR.Anderson@amd.com>
Subject: Re: Strange match to my query
In-Reply-To: <AANLkTikzBkHoTUO41byUrZrTPk1YUgG+rDPKtsTSq2sy@mail.gmail.com>
References: <3wd4o8wa7fx.fsf@testarossa.amd.com>
	<AANLkTikzBkHoTUO41byUrZrTPk1YUgG+rDPKtsTSq2sy@mail.gmail.com>
User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1
	(i486-pc-linux-gnu)
Date: Wed, 26 Jan 2011 12:19:17 +1000
Message-ID: <8762tc2yqi.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: notmuch@notmuchmail.org
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Tue, 25 Jan 2011 19:51:14 -0500, Austin Clements <amdragon@gmail.com> wr=
ote:
> Well-constructed test message.  Xapian's query parser is actually doing t=
he
> right thing [1] and this is a bug in the way notmuch indexes address list
> headers.  For each address, _notmuch_message_gen_terms resets the term
> generator's term position, so your To header indexes with positions as
>   c:1 hello:2 com:3 K:1 R:2 world:3 com:4

Thanks, Austin!

I was actually giving a demo of notmuch to someone yesterday who was
really interested in the details of how Xapian actually stores things.

I dug around a bit with delve and we were both really surprised by the
position results we were seeing. Neither of us could make any sense of
them at all.

And thanks, Mark for the bug report and the nice test case. I'll add
this to the test suite, and fix it. And that will give us yet one more
reason for all of us to rebuild our databases after the upcoming
release.

=2DCarl

=2D-=20
carl.d.worth@intel.com

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFNP4Sl6JDdNq8qSWgRAkRmAJwICXvfIhDZlTKP8OnTjO/AMxQ9RgCfXNoB
qIGc7gNG25Jyk1dwFLq/NzM=
=9G1i
-----END PGP SIGNATURE-----
--=-=-=--