[RFC patch 2/2] lib: index message files with duplicate message-ids
david at tethera.net
Thu Mar 16 17:34:22 PDT 2017
Daniel Kahn Gillmor <dkg at fifthhorseman.net> writes:
> On Wed 2017-03-15 21:57:28 -0400, David Bremner wrote:
>> The corresponding xapian document just gets more terms added to it,
>> but this doesn't seem to break anything.
> this is an interesting suggestion. thanks for proposing it!
> A couple questions:
> 0) what happens when one of the files gets deleted from the message
> store? do the terms it contributes get removed from the index?
That's a good guestion, and an issue I hadn't thought about.
Currently there's no way to do this short of deleting all the terms (for
all the files (excepting tags and properties, presumably) and
reindexing. This will require some more thought, I think.
> 1) when a message is displayed to the user as a result of a match, it
> gets pulled from one of the files, not both. if it's pulled from
> the file that didn't have the term the user searched for, that's
> likely to be confusing. do you have a way to avoid that confusion?
I was looking for an incremental improvement, so I imagined something
like various output flagging "yes, there are duplicate files for this
message", and letting users dig those out using something like the
> It also occurs to me that one of the things i'd love to have is
> well-indexed notes about any given e-mail. So if this was adopted, i
> could presumably just write a file that has the same Message-Id as the
> message, put my notes in it, and index it. that's a little weird,
> though. would there be a better way to do such a thing?
One option would be to use a note=foo mesage property. That's not
immediately searchable though, although we could kludge together
something like the subject regexp search which would be slower.
More information about the notmuch