hm, a GET /dbname/docid where the document is deleted should always return a 
404, can you show a counterexample?

B.

> On 27 Dec 2016, at 05:02, Ian Goodacre <[email protected]> wrote:
> 
> I haven't compacted the database. When I get the document, I am specifying 
> the revision that appears in the output from _changes. This output includes 
> many deleted documents. Most of these I am able to retrieve in this way but 
> there are a few exceptions for which I get the 404 error. Those for which I 
> get the 404 error appear only once in the output from _changes, so I assume 
> the revision is the latest. In any case, something makes these few documents 
> different from the other deleted documents. I don't yet know what has caused 
> them to be different, which is what I would like to know.
> 
> After compacting a database, is it normal for revisions of documents to 
> appear in the output of _changes despite them having been removed from the 
> database and unavailable to get, even with the revision specified? Other than 
> a continuous changes feed, in which a document may appear repeatedly, my 
> observation (not very thorough but I haven't yet seen an exception) has been 
> that each document appears only once and the latest/winning revision appears. 
> It seems odd that an unavailable revision would appear.
> 
> On 26/12/2016 13:35, Robert Newson wrote:
>> Deleted docs return 404 when fetched, that's normal. If you're fetching an 
>> older revision than the latest, it will also be missing if you've compacted 
>> the database.
>> 
>> Sent from my iPhone
>> 
>>> On 24 Dec 2016, at 17:32, Ian Goodacre <[email protected]> wrote:
>>> 
>>> Hi all,
>>> 
>>> I am running CouchDB 1.6.1 on Linux.
>>> 
>>> I have a database that has many deleted documents and I am able to retrieve 
>>> most of these but there are a few that I am unable to retrieve. When I 
>>> attempt to retrieve these, I get 404 with error 'not_found' and reason 
>>> 'missing'.
>>> 
>>> I would like to understand why these few documents are different - why am I 
>>> unable to retrieve these deleted documents?
>>> 
>>> For example, _changes response includes:
>>> 
>>>    {
>>>      "deleted": true,
>>>      "changes": [
>>>        {
>>>          "rev": "2-338d783957e141566caf3662cc0726bb"
>>>        }
>>>      ],
>>>      "id": "assets_0000245",
>>>      "seq": 2355
>>>    },
>>> 
>>> 
>>> When I attempt to retrieve this with:
>>> 
>>> http://localhost:5984/dcm_assets_tp/assets_0000245?rev=2-338d783957e141566caf3662cc0726bb
>>> 
>>> I get a 404 response.
>>> 
>>> I am expecting to get the deleted document, even it if only contains _id, 
>>> _rev and _deleted.
>>> 
>>> Also, I don't understand the response to
>>> 
>>> curl --noproxy '*' -X GET 
>>> 'http://localhost:5984/dcm_assets_tp/assets_0000245?open_revs=all'
>>> 
>>> which is
>>> 
>>> --a341c8902ae323bd6ea7d938bc0c2ac5--
>>> 
>>> And I get the same in response to
>>> 
>>> http://localhost:5984/dcm_assets_tp/assets_0000245?revs=true&open_revs=all
>>> 
>>> But, if I add -H 'Accept: application/json' then I get an empty array ([]):
>>> 
>>> curl --noproxy '*' -X GET -H 'Accept: application/json' 
>>> 'http://localhost:5984/dcm_assets_tp/assets_0000245?open_revs=all'
>>> 
>>> 
>>> I must be misunderstanding something (or a lot of things). Any help would 
>>> be appreciated.
>>> 
>>> Regards,
>>> Ian
>>> 
>> 
> 

Reply via email to