From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] xapian question
Date: Tue, 28 Jul 2009 12:05:39 -0700 [thread overview]
Message-ID: <1248807365-sup-4965@masanjin.net> (raw)
In-Reply-To: <1248795865-sup-6634@pion.club.cc.cmu.edu>
Reformatted excerpts from Rich Lane's message of 2009-07-28:
> Xapian actually provides add_term and remove_term for documents.
Excellent.
> I'd definitely like to use these for label updates, but we need a way
> to tell if only the labels have changed in sync_message.
I've been running into this same issue with my sup-server experiments,
so I think we should split the API into, say, three separate calls:
something like add_new_message, update_labels, and update_body. (AFAIK
the only client of update_body is in some of the draft editing stuff.)
WDYT?
> Or, we update the index in Message#add_label/etc and get rid of the
> need to save buffers. That might not be an option for the Ferret
> index, though.
I think that would actually be fine for Ferret, and it's a direction
that's often been discussed. (Especially now that we have undo.) If we
do the above, we can certainly do this as a later step.
> We don't store the body in entries.db, just enough info for
> thread-index-mode. It's only about 800 bytes/message for me, but I
> don't have snippets enabled so yours would be larger.
On second glance, it's a little smaller than I remembered. For my sample
212m mbox, it's about 20m with snippets enabled.
The total index size under Xapian (the xapian/ dir and all gdbm files)
is larger than the original mbox file, which seems a little insane. But
hey, disk space is cheap.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-07-28 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:45 William Morgan
2009-07-28 15:57 ` Rich Lane
2009-07-28 19:05 ` William Morgan [this message]
2009-08-01 6:28 ` Rich Lane
2009-08-03 18:03 ` William Morgan
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=1248807365-sup-4965@masanjin.net \
--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