Return-Path: 
 <user-return-19317-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org>
X-Original-To: apmail-couchdb-user-archive@www.apache.org
Delivered-To: apmail-couchdb-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C647397BA
	for <apmail-couchdb-user-archive@www.apache.org>;
 Tue,  3 Jan 2012 15:58:50 +0000 (UTC)
Received: (qmail 29667 invoked by uid 500); 3 Jan 2012 15:58:48 -0000
Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org
Received: (qmail 29637 invoked by uid 500); 3 Jan 2012 15:58:48 -0000
Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@couchdb.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@couchdb.apache.org>
List-Post: <mailto:user@couchdb.apache.org>
List-Id: <user.couchdb.apache.org>
Reply-To: user@couchdb.apache.org
Delivered-To: mailing list user@couchdb.apache.org
Received: (qmail 29621 invoked by uid 99); 3 Jan 2012 15:58:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 15:58:48 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of adam.kocoloski@gmail.com
 designates 209.85.212.52 as permitted sender)
Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 15:58:40 +0000
Received: by vbbfk1 with SMTP id fk1so16717151vbb.11
        for <user@couchdb.apache.org>; Tue, 03 Jan 2012 07:58:19 -0800 (PST)
Received: by 10.52.35.148 with SMTP id h20mr11567742vdj.21.1325606299829;
        Tue, 03 Jan 2012 07:58:19 -0800 (PST)
Received: from [192.168.0.187] (c-24-60-185-198.hsd1.ma.comcast.net.
 [24.60.185.198])
        by mx.google.com with ESMTPS id fe5sm35335410vdc.8.2012.01.03.07.58.17
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 03 Jan 2012 07:58:18 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: Delete replication history
From: Adam Kocoloski <kocolosk@apache.org>
In-Reply-To: 
 <CAL3q7H4WChkJ1Y4HB0ZDO4YF50qAxGciVLohX5EO7j98hE08rQ@mail.gmail.com>
Date: Tue, 3 Jan 2012 10:58:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <71BAE901-B302-49DE-A882-FC76877D0061@apache.org>
References: <54E27482-695C-4DCF-8A49-777F1C7BC93C@sri.com>
 <CAHZBNKZb9WvRn39ApuDu-i8LLLH4EJmj6kaRi4Q0eBv1=ZEEVQ@mail.gmail.com>
 <CABvT1DHj08uq9OanFb7m+86e1b4z-iwjsQSV0LzoH2OTM-qEow@mail.gmail.com>
 <36E79CEC5BFB8E4D9763C4DEB9B1163C38AD61B784@UK-EXCHMBX1.green.sophos>
 <905FBBAC-109D-4624-BBB9-A8BC913E445A@apache.org>
 <CAL3q7H4WChkJ1Y4HB0ZDO4YF50qAxGciVLohX5EO7j98hE08rQ@mail.gmail.com>
To: user@couchdb.apache.org
X-Mailer: Apple Mail (2.1251.1)

On Jan 3, 2012, at 10:41 AM, Filipe David Manana wrote:

> On Tue, Jan 3, 2012 at 3:00 PM, Adam Kocoloski <kocolosk@apache.org> =
wrote:
>> On Jan 3, 2012, at 3:23 AM, Paul Hirst wrote:
>>=20
>>>> -----Original Message-----
>>>> From: Robert Newson [mailto:rnewson@apache.org]
>>>> Sent: 24 December 2011 12:46
>>>> To: user@couchdb.apache.org
>>>> Subject: Re: Delete replication history
>>>>=20
>>>> I believe Jim is referring to the replication checkpoint document
>>>> (which does indeed include 'historical' information). Jim is also
>>>> correct in that the presence of this document will prevent a full
>>>> re-replication when the target's validate_doc_update function is
>>>> altered.
>>>>=20
>>>> Jim, the replication checkpoint document is named in the way:
>>>> /dbname/_local/<hash>. You should be able to see this document =
being
>>>> written to in the logs and the <hash> portion is also the value you
>>>> get back when POST'ing to _replicate (and the one shown in
>>>> _active_tasks). Delete the document in the usual fashion and
>>>> replication will do over from the start.
>>>=20
>>> I've only ever been able to find the hash value in the log. If it's =
in _active_tasks where is it?
>>>=20
>>> My replication entries in _active_tasks look like
>>>=20
>>> ba3959: http://myserver.example:5984/mydb/ -> mydb
>>>=20
>>> And I don't believe ba3959 is long enough. Isn't the hash an MD5 of =
the replication information?
>>>=20
>>> If there was a way to get it out of _active_tasks it would be =
extremely convenient.
>>>=20
>>> Sophos Limited, The Pentagon, Abingdon Science Park, Abingdon, OX14 =
3YP, United Kingdom.
>>> Company Reg No 2096520. VAT Reg No GB 991 2418 08.
>>=20
>>=20
>> Currently _active_tasks only reports the first six characters of the =
hash.  I'm not opposed to having it report the full hash, especially now =
that the _active_tasks output is semi-structured.
>=20
> The branch for the next major release, 1.2.x, already reports the full
> id (unlike all current releases which only report the first 6
> characters in _active_tasks).

Ah, thanks for the correction Filipe!=