[jira] Commented: (COUCHDB-1037) Combining filter and limit in _changes requests produce strange results

["Filipe Manana (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984732#action_12984732 ] 

Filipe Manana commented on COUCHDB-1037:
----------------------------------------

Hi Mikhail,

Thanks for the report and test script. I was able to reproduce it.
Will work on fix as soon as I can.

> Combining filter and limit in _changes requests produce strange results
> -----------------------------------------------------------------------
>
>                 Key: COUCHDB-1037
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1037
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core, HTTP Interface
>    Affects Versions: 1.0.1
>         Environment: Distribution: CRUX-2.7, linux 2.6.37, x86, smp
> CouchDB 1.0.1, icu 4.2.1, spidermonkey 1.7.0, erlang R14A all build from ports (sources), gcc 4.5.2, glibc 2.12.2
>            Reporter: Mikhail Kolesnik
>         Attachments: _changes_filter_limit.sh, _changes_gilter_limit.log
>
>
> To reproduce the problem: 
>   create some doc and filter function with doc_type=="test" criteria (total: 2 docs)
>   create some more docs with {"doc_type":"test"} to match filtering
>   inspect the whole _changes
>   make sure filter function works
>   make sure limit works
>   combine them: 
>      _changes/limit=1&filter=testdocs/testdocsonly - gives empty "results". I guess this should not happen.
>      _changes/limit=2&filter=testdocs/testdocsonly  - works as expected
>   
> actual bash script to test it easily and log output attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.