iterview does not work for views on which you specify reduce in the options. #270

Activity

1. mountainpaul

   changed the title [-]iterview does not work for views on which you specify reduce.[/-] [+]iterview does not work for views on which you specify reduce in the options.[/+] on Jan 1, 2016
2. djc commented on Jan 4, 2016

   

   djc

   on Jan 4, 2016

   Owner

   More actions

   Hmm, it feels like it might work with startkey, but without startkey_docid. Perhaps you can give that a whirl? The iterview() code could only pass startkey_docid if reduce is not specified, or even when id is not available on the resutl.
3. mountainpaul commented on Mar 18, 2016

   

   mountainpaul

   on Mar 18, 2016

   Author

   More actions

   Specifying a startkey does not appear to help. It appears for the first batch that 'id' is available, but on the second batch (i.e. next iteration) the id is not available.
4. mountainpaul commented on Mar 18, 2016

   

   mountainpaul

   on Mar 18, 2016

   Author

   More actions

   Changing client.py at line 870 from

              options.update(startkey=rows[-1]['key'], startkey_docid=rows[-1]['id'])
   to 
              try:
                   options.update(startkey=rows[-1]['key'], startkey_docid=rows[-1]['id'])
              except KeyError: 
                   if rows[-1]['key']!=rows[-2]['key']:
                         options.update(startkey=rows[-1]['key'])
                   else:
                         raise

   fixed my issue, but in my specific case the key was unique because of the group level.
5. nedgar commented on Oct 13, 2016

   

   nedgar

   on Oct 13, 2016

   More actions

   When doing a reduce, isn't each key unique, even for different group levels? Seems like it should be feasible to just omit the startkey_docid when reduce is True. I'm trying this out now.