You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Mikhail Kolesnik (JIRA)" <ji...@apache.org> on 2011/01/21 13:29:44 UTC

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

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


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: http://pastebin.com/eL2Xh4Vr
full script output: http://pastebin.com/1762cVJe

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


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

Posted by "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.


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

Posted by "Mikhail Kolesnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Kolesnik updated COUCHDB-1037:
--------------------------------------

    Description: 
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.

  was:
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: http://pastebin.com/eL2Xh4Vr
full script output: http://pastebin.com/1762cVJe


> 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.


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

Posted by "Mikhail Kolesnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Kolesnik updated COUCHDB-1037:
--------------------------------------

    Attachment: _changes_gilter_limit.log
                _changes_filter_limit.sh

attached actual script and it's log

> 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: http://pastebin.com/eL2Xh4Vr
> full script output: http://pastebin.com/1762cVJe

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


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

Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filipe Manana reassigned COUCHDB-1037:
--------------------------------------

    Assignee: Filipe Manana

> 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
>            Assignee: Filipe Manana
>         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.


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

Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filipe Manana closed COUCHDB-1037.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2
                   1.1

Fix, with a test based on the shell script, applied to trunk, and branches 1.1.x and 1.0.x.

Thanks.

> 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
>            Assignee: Filipe Manana
>             Fix For: 1.1, 1.2
>
>         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.