unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Walters <markwalters1009@gmail.com>
To: Vladimir Marek <Vladimir.Marek@oracle.com>,
	David Edmondson <david.edmondson@oracle.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Deduplication ?
Date: Mon, 02 Jun 2014 15:15:39 +0100	[thread overview]
Message-ID: <87y4xfqtx0.fsf@qmul.ac.uk> (raw)
In-Reply-To: <871tv7s8q1.fsf@qmul.ac.uk>



Mark Walters <markwalters1009@gmail.com> writes:

> Vladimir Marek <Vladimir.Marek@oracle.com> writes:
>
>>> > I want to import bigger chunk of archived messages into my notmuch
>>> > database. It's about 100k messages. The problem is, that I most probably
>>> > have quite a lot of those messages in the DB. Basically I would like to
>>> > add only those I don't have already.
>>> >
>>> > There are two possibilities
>>> >
>>> > a) I will add all the 100k messages and then remove the duplicities.
>>> >
>>> > b) I will write a script which will parse the message ID's of the
>>> >    to-be-added messages and try to match them to the notmuch DB. Adding
>>> >    only files I can't find already.
>>> >
>>> > Ad b) might be better option, but I started to play with the idea of
>>> > deduplication. I'm thinking about listing all the message IDs stored in
>>> > DB, listing all files belonging to the IDs and deleting all but one.
>>> > Also I'm thinking about implementing some simple algorithm telling me
>>> > whether the messages are really very similar. Just to be sure I don't
>>> > delete something I don't want to.
>>> >
>>> > Was anyone playing with the idea?
>>> 
>>> notsync[1] used the (lack of) existence of a message id in the store to
>>> decide whether to add something from an IMAP server, but it is old,
>>> crufty, unused and unloved code.
>>
>> I see, that's close to my b) solution, thanks!
>
> Did you mean a) here? The idea was to add them all first and then run
> this script to delete the duplicates.
>

Sorry: out of order arrival times and lack of care on my part. Sorry!

MW

> Best wishes
>
> Mark
>
>> -- 
>> 	Vlad
>> _______________________________________________
>> notmuch mailing list
>> notmuch@notmuchmail.org
>> http://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2014-06-02 14:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 12:32 Deduplication ? Vladimir Marek
2014-06-02 13:43 ` David Edmondson
2014-06-02 13:54   ` Vladimir Marek
2014-06-02 14:10     ` Mark Walters
2014-06-02 14:15       ` Mark Walters [this message]
2014-06-02 13:51 ` Mark Walters
2014-06-02 14:17   ` Tomi Ollila
2014-06-02 14:26     ` Mark Walters
2014-06-02 17:06       ` Jani Nikula
2014-06-02 17:25         ` David Edmondson
2014-06-02 18:29           ` Jani Nikula
2014-06-06 10:40           ` Vladimir Marek
2014-06-07 13:37             ` Tomi Ollila

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4xfqtx0.fsf@qmul.ac.uk \
    --to=markwalters1009@gmail.com \
    --cc=Vladimir.Marek@oracle.com \
    --cc=david.edmondson@oracle.com \
    --cc=notmuch@notmuchmail.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).