couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-582) _changes filter missing updates
Date Tue, 25 Jun 2013 21:03:20 GMT


Alexander Shorin commented on COUCHDB-582:

Hm..I'd updated to fit modern couchdb-python package, but the result I get on master
head (httplib2-0.8, couchdb-python-0.9) is always:

changes {'last_seq': 2, 'results': [{'changes': [{'rev': '1-cc2a517fa3e1a5b6ae9e3fbea460b9b8'}],
'id': 'one', 'seq': 2}]}
changes {'last_seq': 3, 'results': [{'changes': [{'rev': '1-3ca2f01d11f16acffd9bfc740e4c963b'}],
'id': 'two', 'seq': 3}]}
changes {'last_seq': 4, 'results': [{'changes': [{'rev': '2-7efa0b7c0b924d89349d755a5fea9452'}],
'id': 'two', 'seq': 4}]}
changes {'last_seq': 5, 'results': [{'changes': [{'rev': '3-2b31cf580e9bb5c63d65c7aa3506910a'}],
'id': 'two', 'seq': 5}]}
changes {'last_seq': 6, 'results': [{'changes': [{'rev': '2-4586821503d458100d84e996c3dab9ed'}],
'id': 'one', 'seq': 6}]}
changes {'last_seq': 7, 'results': [{'deleted': True, 'changes': [{'rev': '3-9b9b2cfbd85c1869387ce366e7a1665a'}],
'id': 'one', 'seq': 7}]}
changes {'last_seq': 8, 'results': [{'deleted': True, 'changes': [{'rev': '4-13b322b54c4b9bf87f23c437e43a2f1e'}],
'id': 'two', 'seq': 8}]}

and no missed results fields for multiple runs. Could this issue be eventually fixed? Could
anyone reproduce it?
> _changes filter missing updates
> -------------------------------
>                 Key: COUCHDB-582
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>            Reporter: Chris Anderson
>            Assignee: Chris Anderson
>         Attachments:
> reported on the user mailing list: 
> I know there is work to be done on the filter mechanism (specifically around process
reuse and concurrency)
> The current implementation requires a process per connected user. This should be not
that hard to patch.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message