No, the row is:
{"id":"510427_2011_1","key":["510427",2011,1],"value":1,"doc":null}
Marcello
2011/11/16 Mark Hahn <[email protected]>:
> Does this doc by any chance have an empty _id field? If so that is a known
> problem. It cannot be fixed in a db when it happens. Couch is supposed to
> have a fix soon, if not already.
>
> On Tue, Nov 15, 2011 at 10:57 PM, Marcello Nuccio <[email protected]
>> wrote:
>
>> I've reloaded Futon at least three times...
>>
>> However, the problem is that the row with doc==null is still there,
>> and the only way to get rid of it is to rebuild the view. I will try
>> to find how to reproduce it in a new database.
>>
>> If anyone is interested to see the database, I can send it. It does
>> not contain top secret data, and it's only a couple of MB.
>>
>> I have updated my program to ignore those rows. It is a good thing to
>> do since it can happen if querying with stale=ok.
>>
>> Marcello
>>
>> 2011/11/15 Mark Hahn <[email protected]>:
>> > You have to reload twice to update futon. It is a pita.
>> >
>> > On Tue, Nov 15, 2011 at 5:32 AM, Marcello Nuccio
>> > <[email protected]>wrote:
>> >
>> >> 2011/11/15 Marcello Nuccio <[email protected]>:
>> >> > I've done some more testing:
>> >> >
>> >> > 1. I've restored the original db and view files (before compaction and
>> >> cleanup)
>> >> > 2. I've made a clone of the db and view with new name
>> >> > 3. Verified that everything works as expected, i.e. both db return
>> >> > identical results and all files are identical (done using curl and
>> >> > cmp).
>> >> >
>> >> > Here the tests:
>> >> >
>> >> > 1. Compacting the clone the row with doc==null disappears.
>> >> > 2. Compacting the master the row is still here.
>> >>
>> >> Ops sorry, I did those two tests with Futon and forcing reload did not
>> >> show the row in test 1. After clearing the cache completely, the row
>> >> with doc==null is here.
>> >>
>> >> I verified with curl and both dbs return the row with doc==null.
>> >>
>> >> The only way I have found to delete it, is to delete the view file.
>> >>
>> >> Marcello
>> >>
>> >>
>> >> > 3. Comparing with cmp *.couch and *.view, they are identical.
>> >> > 4. Restarting couchdb does not help.
>> >> >
>> >> > What am I missing?
>> >> >
>> >> > Marcello
>> >> >
>> >> > 2011/11/15 Robert Newson <[email protected]>:
>> >> >> That does sound wrong but not sure what steps to suggest next.
>> >> >>
>> >> >> B.
>> >> >>
>> >> >> On 15 November 2011 12:22, Marcello Nuccio <
>> [email protected]>
>> >> wrote:
>> >> >>> No.
>> >> >>>
>> >> >>> Marcello
>> >> >>>
>> >> >>> 2011/11/15 Robert Newson <[email protected]>:
>> >> >>>> Did you query with stale=ok?
>> >> >>>>
>> >> >>>> B.
>> >> >>>>
>> >> >>>> On 15 November 2011 11:10, Marcello Nuccio <
>> [email protected]>
>> >> wrote:
>> >> >>>>> Don't know how, but I have a view that returns the following row:
>> >> >>>>>
>> >> >>>>>
>> >> {"id":"510427_2011_1","key":["510427",2011,1],"value":1,"doc":null}
>> >> >>>>>
>> >> >>>>> i.e. it has doc==null when queried with include_docs=true. The doc
>> >> >>>>> with the given _id is deleted. The database is compacted. The
>> views
>> >> >>>>> are compacted and cleaned (done via Futon). CouchDB is version
>> 1.1.1
>> >> >>>>> built with build-couchdb on Ubuntu 11.10.
>> >> >>>>>
>> >> >>>>> Is this normal behaviour?
>> >> >>>>>
>> >> >>>>> Thanks,
>> >> >>>>> Marcello
>> >> >>>>>
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >
>>
>
